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/which-command)<a href="https://agentmods.dev/commands/eddiebelaval/squire/which-command"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/which-command/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/which-command"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/which-command.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.02193 |
| Opus 5.5 | $0.00000 | $0.00877 |
| Sonnet 5.5 | $0.00000 | $0.00439 |
| Haiku 4.5 | $0.00000 | $0.00219 |
Grade A, and why
WHICH-COMMAND 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.
How it starts
The opening of the file, as written. The whole thing — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Which Command Should I Use? 🤔
Quick decision tree to pick the right command
Start Here 👇
What's your goal?
│
┌──────────────────┼──────────────────┐
│ │ │
Build Feature Fix Something Understand Something
│ │ │
▼ ▼ ▼
[Keep reading] Use /fix Use /explain
Building a Feature? Ask Yourself...
Question 1: Do you want to learn?
YES - Want to understand HOW and WHY
→ Use /feature-dev
Perfect for:
✅ Learning new concepts
✅ First time with tech
✅ Understanding patterns
✅ Educational experience
Example:
"I want to learn React hooks while building a form"
NO - Just want it done fast
→ Use /start
Perfect for:
✅ You know what to do
✅ Time pressure
✅ Simple features
✅ Repeat patterns
Example:
"Add another button like the existing ones"
Question 2: Do you know what to build?
NO - Still exploring ideas
→ Use /idea first
→ Then /feature-dev or /start
Perfect for:
✅ Brainstorming
✅ Comparing approaches
✅ Figuring out scope
Example:
"I want better notifications but not sure how"
YES - Clear requirements
→ Skip to /feature-dev or /start
Example:
"Add a dark mode toggle in the header"
Quality & Verification Commands
What do you need to check?
│
┌────────────────┼────────────────┐
│ │ │
"Just finished "About to "Deep cleanup
coding" create a PR" between features"
│ │ │
▼ ▼ ▼
/polish /verify /cleanup
│ │ │
│ │ │
▼ ▼ ▼
Auto review + 6-layer audit Dead code,
auto simplify (types, lint, unused files,
in one pass tests, build) config issues
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 · 401 lines · 0 tokens per session scan A 8a934d2d5145
WHICH-COMMAND 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 2,193 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
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:help
Show available PAUL commands and usage guide.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
architect
Generate architecture.md with system design decisions from foundation documents.
analizar-sesiones
Analizar sesiones de Claude en el equipo para extraer patrones de uso y generar recomendaciones de habilidades, plugins, agentes y reglas.
iniciar
Inicializar Don Cheli en un proyecto nuevo o existente.