3 findingsStatic scanned
Runs OpenAI's Codex coding agent locally on your computer from the command line.
71.3M installs/moApache-2.0
Token Guard
allansantos-dev · Agent
Token Guard is a kit of rules, hooks and tools governing what enters an AI agent's context window. An audit command measures what a repository costs in tokens, including the file name listing alone, and another starts the declared MCP servers to measure what they add per session, or only lists them if asked. Hooks block broad scans, blind reads, noisy paths and shell dumps, replace huge tool results with a stub and a saved full copy, and return repeat reads as pointers. It needs only Node and text files; its hooks can start a local background process.
Written by ooruby from the README of @allansantos-dev/token-guard 2.6.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
The context window is fixed while a repository is not, so this governs what is allowed to enter it.
What you could do with it
- Audit a large repository to see how many tokens its file listing alone would cost before the agent reads any code.
- Measure what your declared MCP servers add to each session, with advice per server and tool.
- Install the hooks for your coding agent so oversized tool results are replaced by a stub and a saved full copy.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- node child_process (cli.cjs:17)
- synchronous shell execution (cli.cjs:36)
- node child_process (install.cjs:52)
- synchronous shell execution (install.cjs:366)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
- Data handling disclosed
- finding
- no statement of what it reads, writes or sends (README.md)
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Economia de contexto para agentes de IA, agnóstico de IDE: mede o custo real do repositório em tokens, barra as chamadas que estouram a janela devolvendo sempre a alternativa barata, mede o preâmbulo dos servidores MCP e governa o contrato de saída. Adapt
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 2.6.1, the file with digest sha512-tV1x5zhej8rK+lODr+LZ+TcwME0eyPBUa/NBrk7zlhKhhxtKnKUGzpNIopIx/SAeK/p+p45bW/uImjDt9xHx5Q==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y @allansantos-dev/token-guard@2.6.1Pinned to 2.6.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @allansantos-dev/token-guard
- Version read
- 2.6.1
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/allansantos-dv/token-guard
- Commit
- 73a653367274
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/allansantos-dev-token-guard)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
Similar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.