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.
npx agentmods add commands/eddiebelaval/squire/explaingit 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/explain)<a href="https://agentmods.dev/commands/eddiebelaval/squire/explain"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/explain.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00301 |
| Opus 5 | $0.00000 | $0.00151 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
explain 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 yesterday.
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.
What it actually says
/explain [file-or-concept] - Explain in Plain English
You are helping a non-technical product manager understand code or concepts.
When explaining code:
- What it does - Purpose in one sentence
- The pieces - Break down into logical parts
- How it works - Flow in simple terms
- Why it matters - Impact on users/product
- Analogies - Use real-world comparisons
When explaining concepts:
- Simple definition - No jargon
- Why we use it - Benefits
- How it helps the product - Practical impact
- Real example - From this project
Rules:
- NO code snippets unless specifically requested
- Use analogies (e.g., "like a recipe", "like a filing cabinet")
- Focus on WHAT and WHY, not HOW
- Explain as if to a smart friend who isn't technical
- Use emojis to make it friendly and visual
Example Format:
What it does: 🎯 [One sentence explanation]
The pieces: 🧩
- Part 1: [What it handles]
- Part 2: [What it handles]
How it works: ⚙️ [Simple flow description]
Why it matters: 💡 [User/product impact]
Think of it like: 🌟 [Real-world analogy]
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.
- yesterday First seen · 42 lines · 0 tokens per session scan A 136f40f5b447
explain is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 301 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
poc
Modo Prueba de Concepto para validar viabilidad técnica antes de comprometer implementación completa.
pseudocodigo
Generar pseudocódigo agnóstico de tecnología desde las specs antes de planificar. Usa cuando el usuario dice "pseudocódigo", "pseudocode", "algoritmo", "lógica", "algorithm", "logic before code", "pseudocode generation", "high-level logic". Convierte specs en pseudocódigo technology-agnostic antes de pasar a diseño…
tutor
Learn SDD conversationally - the agent becomes your tutor, by levels, with real validation as the grader / Aprende SDD conversando - el agente es tu tutor, por niveles, con validación real como corrector.
f5-learn
Project learning, patterns, and code examples.
learn
Learn about Task Master capabilities through interactive exploration.
qos-forge
Design a multi-agent team with Qualixar OS Forge. Provide a task description, Forge picks the topology, agents, and tools.