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/eddiebelaval/squire/cleanupgit clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/eddiebelaval/squire/cleanup)<a href="https://agentmods.dev/commands/eddiebelaval/squire/cleanup"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/cleanup.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00505 |
| Opus 5 | $0.00000 | $0.00253 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
cleanup 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 3d 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
/cleanup - Clean Up Project
You are tidying up the project. Be thorough but safe.
Cleanup Checklist:
1. 🗑️ Remove Dead Code
- Unused imports
- Commented-out code
- Unreferenced functions
- Deprecated components Action: Remove (with user confirmation)
2. 📁 Organize Files
- Misplaced files
- Inconsistent naming
- Missing folders Action: Reorganize (show plan first)
3. 📝 Update Documentation
- Outdated README
- Missing component docs
- Old comments Action: Update to match current state
4. 🔧 Config Files
- Unused dependencies in package.json
- Outdated .env.example
- Old configuration Action: Clean up (carefully!)
5. ✅ Tests
- Failing tests
- Outdated test data
- Missing test coverage Action: Fix or remove
6. 🎨 Code Style
- Inconsistent formatting
- Lint warnings
- Naming inconsistencies Action: Standardize
7. 🔒 Security
- Exposed secrets (in git history)
- Insecure patterns
- Outdated dependencies with vulnerabilities Action: Fix immediately
Process:
-
Scan Project
- Identify all cleanup opportunities
- Categorize by priority (critical/nice-to-have)
- Estimate effort
-
Present Findings
Found [count] cleanup opportunities: 🔴 Critical (must fix): - [Issues] 🟡 Recommended: - [Issues] 🟢 Nice-to-have: - [Issues] -
Ask Priority
- Quick cleanup (just critical)
- Standard cleanup (critical + recommended)
- Deep cleanup (everything)
-
Execute Cleanup
- Work through each item
- Commit in logical groups
- Test after each change
-
Report Results
✅ Cleanup Complete! - Files removed: [count] - Files reorganized: [count] - Lines cleaned up: [count] - Issues fixed: [count]
Safety Rules:
- NEVER delete without showing what will be lost
- Always run tests after cleanup
- Commit frequently during cleanup
- Keep user informed of progress
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.
- 3d ago First seen · 95 lines · 0 tokens per session scan A 8233723d24c3
cleanup is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 505 tokens. 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
deck
Turn a markdown planning doc into a spec-grade 기획서 HTML — a buildless, self-contained document by default, or an on-screen slide presentation when you ask for one. Deterministic md→deck transform + a quality/gap lint; the raw markdown travels with it. Use whenever the user wants a planning document turned into…
regression
Run accumulated regression across scv/archive//TESTS.md (and optionally promote/) with supersede/obsolete skip graph. On failure, triage each slug via AskUserQuestion (regression / obsolete / flaky). Use whenever the user asks whether past features still pass, or before archiving anything — 'run the tests', 'is…
routine
Execute one maintenance routine defined in scv/routines/ .md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when…
handoff
Declare that another repo needs corresponding development: write a handoff (+ decision + conversation) into the workspace root scv repo. Multi-repo (nested) only. Use whenever work in this repo implies a change another repo must make — not only when they type /scv:handoff. Never leave that dependency in prose; this…
status
Show raw changes since last index + list of active promote plans. Use whenever the user asks what is in flight, what changed, or where things stand — not only when they type /scv:status. Never summarize project state from memory; this command reads it.
update
Check installed SCV plugin version vs latest release, and guide the user through /plugin marketplace update + /reload-plugins. Read-only — does not modify project files. (v0.11.2+) Use whenever the user asks whether SCV is current or how to update it — not only when they type /scv:update.