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/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/release)<a href="https://agentmods.dev/commands/eddiebelaval/squire/release"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/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.01015 |
| Opus 5 | $0.00000 | $0.00508 |
| Sonnet 5 | $0.00000 | $0.00203 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release — Promote dev to main (production)
You are executing the release workflow for a project with a dev → main branch protocol.
Arguments
$ARGUMENTS
Parse $ARGUMENTS:
- Empty → Standard release (dev → main)
- "dry-run" → Show what would ship, but don't merge
- "hotfix" → Hotfix release (current branch → main, then sync to dev)
Pre-flight: Confirm Location
- Verify you're in a project repo (not ~/Development root)
- Confirm the project name and directory
- Check that
mainanddevbranches exist on the remote - If on a feature branch, switch to
devfirst (unless hotfix mode)
Phase 1: What's Shipping
# Show all commits on dev that aren't on main
git fetch origin
git log origin/main..origin/dev --oneline --no-merges
# Show file-level diff
git diff origin/main..origin/dev --stat
Present to the user:
- Number of commits shipping
- List of PRs included (parse from merge commits)
- File count and summary of changes
- Flag any risky files (API routes, migrations, auth, billing)
If there are NO differences between main and dev:
- Report "Nothing to release — dev and main are in sync."
- Stop.
Phase 2: Pre-flight Checks
Run these in the project directory on the dev branch:
# 1. Type check
npx tsc --noEmit
# 2. Lint (if available)
npm run lint 2>/dev/null
# 3. Tests (if available)
npm test 2>/dev/null || npx vitest run 2>/dev/null
# 4. Build (skip if env vars are needed for prebuild scripts)
# Only run if the build script doesn't require external services
Report results:
PRE-FLIGHT CHECK
TypeScript: PASS/FAIL (N errors)
Lint: PASS/FAIL/SKIPPED
Tests: PASS/FAIL/SKIPPED (N passed, N failed)
Build: PASS/FAIL/SKIPPED
If any FAIL: stop and report. Do NOT proceed to merge. If dry-run mode: stop here after showing the report.
Phase 3: Create Release PR
gh pr create --base main --head dev \
--title "release: [brief description of what's shipping]" \
--body "[changelog generated from Phase 1]"
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 · 139 lines · 0 tokens per session scan A bdb8cf8d778e
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,015 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
update-changelog
Update CHANGELOG.md with new entry based on git diff.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
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…
deploy
/forge:deploy is the safety-first deployment command. Before any deployment action occurs, it runs a five-point pre-flight validation: TypeScript compilation, full test suite, security audit, git cleanliness check, and production build. Each check produces a PASS or FAIL result, and the overall verdict is READY or NOT…
deploy
Deploy the Kernel project to GitHub Pages.
generate-release-notes
Generate user-focused release notes between two versions.