Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/alchemyplatform/alchemy-claude-plugin/tokengit clone --depth 1 https://github.com/alchemyplatform/alchemy-claude-pluginWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00007 | $0.00143 |
| Opus 5 | $0.00003 | $0.00072 |
| Sonnet 5 | $0.00001 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
token scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Look up the token in "$ARGUMENTS".
- If the input is a symbol (e.g. ETH, USDC), call
getTokenPricesBySymbol. - If it's a contract address, call
getTokenPricesByAddress(default networketh-mainnet) andgetTokenMetadatafor name/symbol/decimals/logo. - An app must be selected first for address-based lookups (
/alchemy:setupif needed). Symbol prices may work without a selected app.
Report the current price, 24h change if available, and key metadata.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 13 lines · 7 tokens per session scan A 858a3d313a85
token is a command published in the GitHub repository alchemyplatform/alchemy-claude-plugin (6 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 143 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
squash-bugbot
../../.agents/skills/squash-bugbot/SKILL.md.
audit
Full security audit of a Solidity/Vyper/Rust contract or directory. Runs the entire vuln-skills library and dispatches DeFi specialist subagents based on detected protocol type.
audit-deps
Audit third-party dependencies — resolve installed versions, cross-reference known-vulnerable releases, and flag vendored code that has diverged from upstream.
audit-live
Audit a deployed contract on a live chain. Pulls verified source from the block explorer, optionally forks the chain for live-state simulation.
audit-multi-chain
Diff the on-chain configuration of one contract deployed across multiple chains — owner, oracle, fees, timelock, pause state, proxy impl — and flag the chain that drifted.
bounty-submit
Submit a finding to a bug-bounty platform (Immunefi, Cantina) automatically.