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/announce-releasegit 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/announce-release)<a href="https://agentmods.dev/commands/eddiebelaval/squire/announce-release"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/announce-release.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.1 | $0.00000 | $0.01599 |
| Opus 5 | $0.00000 | $0.00800 |
| Sonnet 5 | $0.00000 | $0.00320 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
announce-release 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/announce-release - Full Release Announcement Pipeline
Orchestrates the complete release announcement: essay generation, website publishing, and social distribution.
Usage
/announce-release <version> "<features summary>"
/announce-release v1.2.0 "New dashboard with real-time metrics"
/announce-release --research "<topic>" # For research articles instead
Pipeline Stages
Stage 1: Content Generation
┌─────────────────────────────────────┐
│ /write-release OR /write-research │
│ Apply Eddie's voice profile │
│ Generate full MDX content │
└─────────────────────────────────────┘
↓
[Review content]
↓
Stage 2: Website Publishing
┌─────────────────────────────────────┐
│ /publish-essay │
│ Create MDX file in id8labs-hub │
│ Git commit and push │
│ Trigger Vercel deploy │
└─────────────────────────────────────┘
↓
[Wait for deploy ~60s]
↓
Stage 3: Social Distribution
┌─────────────────────────────────────┐
│ /post-tweet (X/Twitter) │
│ Generate thread from essay │
│ Optimize with x-viral-optimizer │
│ Post to @id8labs │
└─────────────────────────────────────┘
↓
┌─────────────────────────────────────┐
│ /post-linkedin │
│ Adapt essay for LinkedIn format │
│ Post to Eddie's profile │
│ Add hashtags in comment │
└─────────────────────────────────────┘
Process
-
Generate Content
- If release: Run
/write-release <version> "<summary>" - If research: Run
/write-research "<topic>" - Display content for review
- Allow edits before proceeding
- If release: Run
-
Confirm Publication
- Show essay title, slug, category
- Confirm ready to publish
- User approval required before git push
-
Publish to Website
- Run
/publish-essay - Wait for Vercel deploy completion
- Verify essay URL is accessible
- Run
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 · 229 lines · 0 tokens per session scan A 939fc80ad6cd
announce-release 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 1,599 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
paul:help
Show available PAUL commands and usage guide.
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…
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.