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/command-map)<a href="https://agentmods.dev/commands/eddiebelaval/squire/command-map"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/command-map/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/command-map"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/command-map.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.02124 |
| Opus 5.5 | $0.00000 | $0.00850 |
| Sonnet 5.5 | $0.00000 | $0.00425 |
| Haiku 4.5 | $0.00000 | $0.00212 |
Grade A, and why
command-map 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Command Map 🗺️
Your complete command ecosystem at a glance
YOUR SLASH COMMANDS
🎮
|
┌───────────────────┼───────────────────┐
| | |
🎬 START 🔨 BUILD 🚀 SHIP
| | |
┌───┴───┐ ┌────┴────┐ ┌───┴───┐
| | | | | | |
/start /idea /test /fix /preview /ship /docs
|
/explain
🎯 Command Categories
🎬 STARTING PHASE
┌─────────────────────────────────────┐
│ /start [name] │
│ → Create branch │
│ → Plan feature │
│ → Ready environment │
│ │
│ /idea │
│ → Brainstorm approaches │
│ → Evaluate options │
│ → Pick best path │
└─────────────────────────────────────┘
🔨 BUILDING PHASE
┌─────────────────────────────────────┐
│ /test │
│ → Visual browser testing │
│ → Automated verification │
│ → Screenshots & reports │
│ │
│ /fix │
│ → Debug systematically │
│ → Root cause analysis │
│ → Verify fix works │
│ │
│ /explain [thing] │
│ → Plain English explanations │
│ → No jargon │
│ → Real-world analogies │
└─────────────────────────────────────┘
📊 INFORMATION PHASE
┌─────────────────────────────────────┐
│ /status │
│ → Project state │
│ → Progress report │
│ → Quality checks │
│ │
│ /compare │
│ → What changed │
│ → Impact assessment │
│ → Visual diffs │
│ │
│ /preview │
│ → Review before commit │
│ → Quality gates │
│ → Visual verification │
└─────────────────────────────────────┘
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 · 403 lines · 0 tokens per session scan A 021b60379c1c
command-map 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,124 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.