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/cheatsheetgit 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/cheatsheet)<a href="https://agentmods.dev/commands/eddiebelaval/squire/cheatsheet"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/cheatsheet.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.00793 |
| Opus 5 | $0.00000 | $0.00396 |
| Sonnet 5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
cheatsheet 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slash Commands Cheatsheet 🎯
Quick reference for your custom commands
One-Line Descriptions
| Command | What It Does |
|---|---|
/feature-dev |
🎓 Complete learning workshop - builds & teaches |
/start [name] |
Create feature branch & plan work |
/idea |
Brainstorm approaches before building |
/test |
Verify feature works (uses Playwright) |
/fix |
Debug and fix issues |
/preview |
Review changes before commit |
/status |
Show project state & progress |
/explain [thing] |
Understand code in plain English |
/compare |
See what changed |
/ship |
Complete feature & create PR |
/docs |
Generate documentation |
/cleanup |
Tidy up project |
/rollback |
Undo recent changes |
When to Use What
🚀 Starting Something New
/feature-dev → Want to LEARN while building
/start feature-name → Fast start (already know how)
/idea → Still figuring it out
🔨 While Building
/test → Check if it works
/fix → Something's broken
/explain → Don't understand something
✅ Before Committing
/preview → Review all changes
/status → Check overall state
🎉 Ready to Ship
/docs → Document what you built
/ship → Create PR & deploy
🛠️ Maintenance
/cleanup → Clean up code
/rollback → Undo changes
/compare → See differences
Most Common Workflows
Build New Feature (Learning Mode)
1. /feature-dev
2. [Answer questions]
3. [Learn as it builds]
4. [Ships automatically]
Build New Feature (Fast Mode)
1. /start feature-name
2. [Describe what you want]
3. /test
4. /preview
5. /ship
Fix a Bug
1. /fix
2. [Describe the problem]
3. /test
4. /ship
Explore an Idea
1. /idea
2. [Describe your vision]
3. [Pick an approach]
4. /start feature-name
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 · 165 lines · 0 tokens per session scan A c4a7de59faa9
cheatsheet 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 793 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
paul:help
Show available PAUL commands and usage guide.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
paul:verify
Guide manual user acceptance testing of recently built features.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
doncheli-status
Show current project status — phase, progress, coverage, gates.
docs-update
/forge:docs-update is the documentation fixer. It compares recently changed source files (from the last 20 commits or 7 days) against documentation files to find staleness, then reads both the outdated doc and the current source code to identify discrepancies -- new functions, changed interfaces, removed features. For…