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/prep)<a href="https://agentmods.dev/commands/eddiebelaval/squire/prep"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/prep/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/prep"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/prep.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.00642 |
| Opus 5 | $0.00000 | $0.00321 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
prep 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 5d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/prep - Research Doc Creation
You are helping create a new prep (research/investigation) document in the current project's workspace. This is a conversational process — you interview the user to understand what they're researching and why, then create a pre-filled document they can build on.
Arguments
- $ARGUMENTS: Topic description (can be rough)
- Flags:
--type <architecture|api|competitor|tech-stack|cost|security>,--project <name>
Conversational Flow
Phase 1: Classify the Research (use AskUserQuestion)
If --type wasn't provided, ask:
-
Research Type — What kind of investigation? Options:
- Architecture Research (exploring system design options)
- API Evaluation (evaluating a service or API)
- Competitor Analysis (analyzing competition)
- Tech Stack Evaluation (comparing technologies)
- Cost Analysis (modeling costs)
- Security Review (assessing security posture)
-
Project — Which project? (if not auto-detected)
Phase 2: Understand the Research Question (conversational)
Ask naturally based on the type:
For Architecture Research:
- "What specific question are you trying to answer?"
- "What's the current state — what exists today?"
- "What options are you already considering?"
For API Evaluation:
- "Which service or API are you looking at?"
- "What problem will it solve for you?"
- "Any alternatives you're already aware of?"
For Tech Stack Evaluation:
- "What category of tool? (e.g., auth library, state management, ORM)"
- "What are the candidates you know about?"
- "What matters most — performance, DX, cost, community?"
For Competitor Analysis:
- "Who is the competitor?"
- "What aspect are you most interested in — features, pricing, positioning?"
For Cost Analysis:
- "What infrastructure are you evaluating?"
- "What's driving this — scaling, optimization, or new service?"
For Security Review:
- "What's the scope — a specific feature, an API, the whole app?"
- "Any specific concerns that triggered this?"
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.
- 5d ago First seen · 73 lines · 0 tokens per session scan A a11c4b3b4a23
prep is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 642 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-09-03.
Other commands, from other repositories
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.
analizar-sesiones
Analizar sesiones de Claude en el equipo para extraer patrones de uso y generar recomendaciones de habilidades, plugins, agentes y reglas.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
iniciar
Inicializar Don Cheli en un proyecto nuevo o existente.
archivar
Archivar specs completadas y sincronizar delta specs con specs principales.