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.
git 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/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/eddiebelaval/squire/cleanup"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/cleanup.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.00000 | $0.00505 |
| Opus 5.5 | $0.00000 | $0.00202 |
| Sonnet 5.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 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.
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.
- 1mo 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 2mo 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
investigate-sentry-issue
Investigate and triage a Sentry error issue.
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
ci-sentinel
Daily autonomous classifier for failing PRs across your repos. Runs /ci-debug headless against every open PR with red required checks, posts the verdict as a collapsed PR comment, and appends to a per-repo .sentinel/ledger.jsonl. v1 is propose-don't-apply — NEVER auto-pushes a fix. Use when you're tired of /status…
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
deadcode.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.
optimize
Analyze and optimize codebase for performance and maintainability.