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/getting-started)<a href="https://agentmods.dev/commands/eddiebelaval/squire/getting-started"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/getting-started/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/getting-started"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/getting-started.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.01909 |
| Opus 5.5 | $0.00000 | $0.00764 |
| Sonnet 5.5 | $0.00000 | $0.00382 |
| Haiku 4.5 | $0.00000 | $0.00191 |
Grade C, and why
GETTING-STARTED scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.claude/commands How it starts
The opening of the file, as written. The whole thing — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Getting Started with Your Slash Commands
Welcome to your personal command center! 🎮
🎯 What Are Slash Commands?
Think of them as macros or shortcuts for common tasks. Instead of explaining the same things over and over, just type a command and Claude knows exactly what to do.
Without Commands:
You: "I want to build a new feature. First create a branch,
then plan it out, make sure dependencies are installed,
and set up the structure..."
Claude: "OK, let me..." [Long back and forth]
With Commands:
You: /start new-feature
Claude: ✅ Branch created
✅ Dependencies checked
✅ Plan created
Ready to build!
🚀 Try Your First Command
Let's test it right now!
Step 1: Test the /status command
Just type in chat:
/status
This shows your current project state. Try it!
Step 2: Try /explain
Type:
/explain what is a component
See how it explains in simple terms? That's the power of custom commands.
💡 The 5 Commands You'll Use Most
1️⃣ /start [feature-name]
Use when: Beginning any new feature
Example:
/start user-notifications
What happens: Creates branch, checks setup, plans work
2️⃣ /test
Use when: Need to verify something works
Example:
/test
Check if signup form works on mobile
What happens: Opens browser, tests it, reports results
3️⃣ /fix
Use when: Something's broken
Example:
/fix
Button doesn't click
What happens: Investigates, finds issue, fixes it, tests
4️⃣ /preview
Use when: Before committing changes
Example:
/preview
What happens: Shows what changed, runs checks, confirms ready
5️⃣ /ship
Use when: Feature is done, ready to deploy
Example:
/ship
What happens: Commits, creates PR, ready for review
🎬 Your First Complete Workflow
Let's build a simple feature end-to-end:
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 · 422 lines · 0 tokens per session scan C ba83ba6155c4
GETTING-STARTED 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 1,909 tokens. A static security scan graded it C with 1 finding (recursive force delete). 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.