Claude Code Spec Workflow is a set of Claude Code commands and agents that organizes software work into documented stages for new features and bug fixes. It is for developers who want Claude Code to handle requirements, design, implementation, issue resolution, and verification through repeatable workflows, with the catalogue entries providing the associated commands and agents.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/elementalsouls/Claude-BugHunternpx agentmods add commands/elementalsouls/claude-bughunter/token-scanWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/elementalsouls/claude-bughunter/token-scan)<a href="https://agentmods.dev/commands/elementalsouls/claude-bughunter/token-scan"><img src="https://agentmods.dev/badge/commands/elementalsouls/claude-bughunter/token-scan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/elementalsouls/claude-bughunter/token-scan"><img src="https://agentmods.dev/badge/commands/elementalsouls/claude-bughunter/token-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00079 | $0.01334 |
| Opus 5.5 | $0.00032 | $0.00534 |
| Sonnet 5.5 | $0.00016 | $0.00267 |
| Haiku 4.5 | $0.00008 | $0.00133 |
Grade A, and why
token-scan 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- token-scan — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/token-scan
Fast rug pull detection for meme coins and token contracts. Covers EVM (Solidity) and Solana (Rust/Anchor).
Usage
/token-scan contracts/Token.sol # Single EVM contract
/token-scan src/ --recursive # Scan entire directory
/token-scan programs/token/ --chain solana --recursive # Solana program
/token-scan contracts/Token.sol --output findings/report.md # Save report
Step 0: Quick Kill Signals
Before scanning code, check:
[ ] Contract is verified (source code available)?
[ ] Deployer has no rug history?
[ ] Token has been trading > 1 hour?
[ ] Liquidity > $5K?
[ ] Not a proxy with retained admin?
If ANY answer is NO → flag and proceed with extreme caution.
Step 1: Optional Automated Scanner
Optional accelerator — not bundled by default. If you have a local
token_scanner.py(or any rug-vector scanner) on PATH, run it first for a quick risk score. If you don't, skip straight to Step 2 — the manual 8-class grep audit below is the real, self-contained check and needs no extra tooling.
# If present:
python3 tools/token_scanner.py <contract_path> # EVM
python3 tools/token_scanner.py <program_dir> --chain solana --recursive # Solana
The manual audit (Steps 2-9) covers all 8 bug classes via grep and is sufficient on its own.
Step 2: Hidden Mint Check
grep -rn "function mint\|_mint(\|_balances\[.*\] +=" src/ --include="*.sol" | grep -v "test\|lib"
grep -rn "delegatecall" src/ --include="*.sol"
# Solana:
grep -rn "MintTo\|mint_to\|mint_authority" src/ --include="*.rs"
Look for: mint without MAX_SUPPLY cap, direct balance manipulation, delegatecall to unknown targets.
Step 3: Honeypot Check
grep -rn "blacklist\|isBlacklisted\|_bots\|maxTxAmount\|approve.*override" src/ --include="*.sol"
# Solana:
grep -rn "freeze_authority\|transfer_hook\|permanent_delegate" src/ --include="*.rs"
Look for: blacklist mappings, max tx setters without minimum bound, approve overrides that don't call super.
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.
- 1mo ago First seen · 141 lines · 0 tokens per session scan A 1dcb13bb9d14
token-scan is a command published in the GitHub repository elementalsouls/Claude-BugHunter (4,874 stars, last pushed 6d ago), licensed MIT. It adds 79 tokens to every session and 1,334 once invoked, about $0.0003 per session on Opus 5.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-30.
Other commands, from other repositories
web3-audit
Smart contract security audit — runs through 10 bug class checklist (accounting desync, access control, incomplete path, off-by-one, oracle errors, ERC4626, reentrancy, flash loan, signature replay, proxy/upgrade). Applies pre-dive kill signals first. Generates Foundry PoC template for confirmed findings. Usage…
token-scan
Meme coin and token security scan — checks for rug pull vectors (hidden mint, honeypot, fee manipulation, LP lock bypass, authority retention, bonding curve exploits, fake renounce, sandwich amplification). Runs automated tokenscanner.py + manual 8-class audit. Usage: /token-scan [--chain solana].
bypass-403
Probe a 403/401 endpoint with the most-paid bypass tricks (header injection, path encoding, method swap, WAF fingerprint, vendor-specific). Wraps byp4xx when installed; otherwise runs a built-in matrix of 38+ techniques. Usage: /bypass-403 | /bypass-403 -l.
spray
Password spray with hard guards — typed-hostname confirmation, lockout warning, audit log. Modes: http-form (custom login page), oauth (password grant), o365 + okta (via TREVORspray). Default delay 30min/round + 60s jitter. Usage /spray --mode --users --passes.
autopilot
Run autonomous hunt loop on a target — scope check → recon → rank surface → hunt → validate → report with configurable checkpoints. Usage: /autopilot target.com [--paranoid|--normal|--yolo].
breach-check
HIBP k-anonymity check on a password wordlist. Enriches each password with its breach count, ranks DESC. Free API (no key), only first 5 chars of SHA-1 sent. Output -> -ranked.txt. Usage /breach-check [--min-count N] [--max-count N] [--with-counts].