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/write-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/write-release)<a href="https://agentmods.dev/commands/eddiebelaval/squire/write-release"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/write-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 | $0.00000 | $0.00900 |
| Opus 5 | $0.00000 | $0.00450 |
| Sonnet 5 | $0.00000 | $0.00180 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
write-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 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/write-release - Generate Release Announcement Essay
Generate a release announcement essay in Eddie's voice for id8labs.app.
Usage
/write-release <version> "<features summary>"
/write-release v1.2.0 "New dashboard with real-time metrics"
/write-release --context # Use recent git commits for context
Process
-
Gather Context
- Version number and features from arguments
- If --context flag, read recent commits from the project
- Check for existing release notes or changelog
- Identify the "why" behind the release (not just "what")
-
Apply Eddie's Voice Profile
Reference
~/.claude/CLAUDE.mdfor voice guidelines:Structure Pattern:
- Visceral opening (sound, confession, unexpected entry)
- Personal context (where we've been, what shaped this)
- Observation/Pattern (what we're seeing)
- Universal connection (your story is everyone's story)
- Call to collective action (invitation to join)
- Warm direct close (love, gratitude, solidarity)
Signature Moves:
- Open unexpected (something visceral or pattern-breaking)
- Hardship as credentials ("This last year has done work on my outlook...")
- Rhetorical questions that build
- Movement from I to We
- Direct loving address at the end
-
Generate MDX Content
--- title: "[Compelling title - not just version number]" subtitle: "[Supporting tagline that expands on value]" date: "[YYYY-MM-DD]" author: "Eddie Belaval" category: "release" tags: ["release", "v{version}", "{product}"] featured: true ---Content should be 800-1500 words covering:
- The problem we were solving (personal story)
- What we built and why it matters (features as benefits)
- How it connects to larger mission (pattern recognition)
- Invitation to try it / join the journey
-
Output
- Display full MDX content for review
- Suggest a filename slug (kebab-case)
- Offer to proceed with /publish-essay
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 · 122 lines · 0 tokens per session scan A 88de581b5b38
write-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 900 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
commit
Creates commits with Conventional Commits format (feat/fix/docs/refactor/test/chore), automatic scope detection, co-author attribution, and pre-commit hook compliance. Validates staged changes, generates descriptive messages focusing on the 'why', and prevents secrets or generated-only files from being committed.…
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
guardian
Revisión de código IA como pre-commit hook — Guardian Angel.
sprint-close
Close the current sprint — build, test, update sprint docs, commit (optional push).
repo-cleanup
Commit accumulated spec doc changes: survey, group by logical batch, branch, commit, merge.
commit
Review the current git diff and generate a thoughtful commit.