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/adr)<a href="https://agentmods.dev/commands/eddiebelaval/squire/adr"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/adr/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/adr"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/adr.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.00710 |
| Opus 5.5 | $0.00000 | $0.00284 |
| Sonnet 5.5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
adr 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/adr - Architecture Decision Record
You are helping create a new ADR (Architecture Decision Record). This is a conversational process — you interview the user about the decision, then create a filled-in record. ADRs capture the WHY behind technical choices so future-you understands the reasoning.
Arguments
- $ARGUMENTS: Decision title or topic (can be rough)
- Flags:
--project <name>
Conversational Flow
Phase 1: Project Context (use AskUserQuestion if needed)
- Project — Which project? (if not auto-detected)
- Status — Options: Proposed (still deciding), Accepted (decided, moving forward)
Phase 2: The Decision Interview (conversational)
Walk through these naturally — don't dump all questions at once:
-
Context: "What's the situation? What problem or need led to this decision?"
- Get the background: what exists today, what's not working, what changed
-
Decision: "What did you decide (or are you proposing)?"
- Get the specific choice: which technology, which pattern, which approach
-
Why this over alternatives: "What else did you consider? Why not those?"
- For each alternative: what was it, what was good about it, why you didn't pick it
- This is the most valuable part of an ADR — the rejected alternatives
-
Consequences: "What are the trade-offs? What does this enable, and what does it cost?"
- Positive: what gets better
- Negative: what gets harder or what you lose
- Neutral: side effects that are neither good nor bad
Phase 3: Create and Fill
- Run
~/.claude/generators/new-adr.shwith the title and project - Read the created file
- Fill in ALL sections from the conversation — Context, Decision, Consequences, Alternatives
- Write the completed file
- Show a summary
Example Conversation
User: /adr Use Supabase RLS instead of API middleware for auth
Claude: Which project is this for?
User: Homer
Claude: What led to this decision? What's the current auth setup?
User: Right now we check user_id in every API route manually. It's repetitive and we already missed one route which caused the IDOR bug last week.
Claude: That's a clear motivator. Did you consider anything besides RLS?
User: Yeah, we thought about a middleware wrapper function, but RLS means the database itself enforces it so even if we forget in the API layer, data is still protected.
Claude: What's the downside of RLS?
User: Harder to debug when queries return empty — you don't know if it's a data issue or a policy issue. Also more complex SQL.
Claude: [Creates ADR-0002-use-supabase-rls-instead-of-api-middleware.md with everything filled in]
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 · 73 lines · 0 tokens per session scan A d090d52ca757
adr 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 710 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.
minar-referencias
Buscar repos open-source relevantes como referencia antes de implementar.