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/write-research)<a href="https://agentmods.dev/commands/eddiebelaval/squire/write-research"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/write-research/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/write-research"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/write-research.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.00928 |
| Opus 5 | $0.00000 | $0.00464 |
| Sonnet 5 | $0.00000 | $0.00186 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
write-research 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/write-research - Generate Research Article Essay
Generate a research article in Eddie's voice for id8labs.app's Research category.
Usage
/write-research "<topic>"
/write-research "Why most productivity tools fail knowledge workers"
/write-research --from-notes <file> # Generate from research notes
When to Use
Research articles are for insights discovered during the building process:
- Market research and competitive analysis
- Technical deep-dives worth sharing
- Patterns observed across users/products
- Philosophical observations about the industry
- "What we learned building X" retrospectives
Process
-
Gather Research Context
- Topic and core thesis from arguments
- If --from-notes, read the source file
- Identify 3-5 key insights or data points
- Find the deeper pattern (the "why behind the why")
-
Apply Eddie's Voice Profile
Reference
~/.claude/CLAUDE.md:Research-Specific Moves:
- Pattern recognition across domains (charts to Buddha, fungi to neural networks)
- Etymology and Latin roots for key concepts
- Connect the micro to the macro
- Personal story that illustrates the research
Structure for Research:
- Hook with unexpected observation or personal confession
- "What I was looking for..." (the question that started this)
- Discovery process (share the journey, not just conclusions)
- Pattern connection (how this relates to larger truths)
- Actionable insight (what this means for the reader)
- Open-ended close (invitation to think alongside)
-
Generate MDX Content
--- title: "[Insight-driven title, not topic-driven]" subtitle: "[The unexpected conclusion or question]" date: "[YYYY-MM-DD]" author: "Eddie Belaval" category: "research" tags: ["research", "{topic}", "{related-concepts}"] ---Content should be 1000-2000 words:
- Personal entry point into the research
- Data/observations (but stories, not just stats)
- Pattern recognition moment
- Connection to reader's experience
- Philosophical or actionable takeaway
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 · 129 lines · 0 tokens per session scan A 83ea18e7654a
write-research is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 928 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.