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/fusengine/agents/cleanup-contextgit clone --depth 1 https://github.com/fusengine/agentsWhat 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.00018 | $0.00369 |
| Opus 5 | $0.00009 | $0.00185 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
cleanup-context 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 yesterday.
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
Cleanup Context
Executes the automatic cleanup script for Claude Code context.
Script Automatique
Run complete cleanup:
~/.claude/scripts/cleanup-context.sh
What Gets Cleaned (PERMANENT DELETION):
- file-history/ - Files >7 days deleted
- history.jsonl - Deleted and reset
- hook-debug.log - Deleted and reset
- security.log - Deleted and reset
- session-env/ - Sessions >30 days deleted
- projects/ - Files >60 days deleted
- statsig/ - Completely emptied
- todos/ - Files >30 days deleted
⚠️ No backup - Permanent deletion
Cleanup Report
The script displays:
- BEFORE state (number of files, lines, size)
- Actions performed
- AFTER state
- Summary of deletions/archives
Example output:
🧹 Claude Code context cleanup
📊 BEFORE cleanup state:
File history: 1234 files
History.jsonl: 5678 lines
Sessions: 89 files
Total size: 245MB
🗑️ Cleaning file-history (>7 days)...
✓ 856 files deleted
🗑️ Deleting history.jsonl...
✓ Deleted and reset
✅ Cleanup complete!
📈 Summary:
File history: 856 files deleted
Sessions deleted: 34
Logs deleted: hook-debug.log, security.log, history.jsonl
Example Usage:
/cleanup-context→ Run complete cleanup
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.
- yesterday First seen · 66 lines · 18 tokens per session scan A a89c7300b881
cleanup-context is a command published in the GitHub repository fusengine/agents (25 stars, last pushed 28d ago), licensed MIT. It adds 18 tokens to every session and 369 once invoked, about $0.0001 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-30.
Other commands, from other repositories
burn-rate
Compute the recent 7-day spend trend (burn rate) from daily sessions and per-session cost.
profile
Coordinate a reproducible Java profiling and optimization lifecycle.
update-issue
Update an issue description with structured, evidence-backed content.
publish-skill
Sync a marketplace skill to the documentation site. Creates skill detail pages (EN/ZH), updates the marketplace index, and updates docs.json navigation.
deploy
Deploy Solana program (devnet first, then mainnet).
generate-idl-client
Generate TypeScript client from Solana program IDL using Codama or Anchor.