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/Habib0x0/spec-driven-pluginWrote 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/habib0x0/spec-driven-plugin/spec-release)<a href="https://agentmods.dev/commands/habib0x0/spec-driven-plugin/spec-release"><img src="https://agentmods.dev/badge/commands/habib0x0/spec-driven-plugin/spec-release/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/habib0x0/spec-driven-plugin/spec-release"><img src="https://agentmods.dev/badge/commands/habib0x0/spec-driven-plugin/spec-release.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.00013 | $0.01049 |
| Opus 5.5 | $0.00005 | $0.00420 |
| Sonnet 5.5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
spec-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 1mo 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-release Command
Prepare a feature for release by generating changelog entries, migration checklists, environment variable documentation, and deployment steps. Optionally creates a git tag and GitHub release.
Philosophy
The gap between "all tasks complete" and "shipped" is where things break. This command makes deployment preparation systematic — no forgotten migrations, missing env vars, or undocumented breaking changes.
Workflow
1. Locate the Spec
If a spec name is provided, use it. Otherwise auto-detect from .claude/specs/.
2. Gather Release Context
Read the spec files and codebase to collect:
From tasks.md:
- All completed tasks (these become changelog items)
- Task descriptions and requirement tracebacks
From design.md:
- Data model changes (migrations needed?)
- New environment variables
- External service dependencies
- Breaking changes to existing APIs
From requirements.md:
- User-facing changes (for user-facing changelog)
- Non-functional changes (for ops changelog)
From acceptance.md (if exists, from /spec-accept):
- Acceptance status and any conditions
From git log:
- All commits related to this feature (scan for spec name or task IDs)
- Authors who contributed
3. Ask Release Configuration
Use AskUserQuestion:
Version bump type:
- Patch (bug fix, no breaking changes)
- Minor (new feature, backwards compatible)
- Major (breaking changes)
Release scope:
- Full release — Changelog, deployment checklist, env vars, migrations
- Changelog only — Just the changelog entry
- Deployment checklist only — Just the ops checklist
4. Generate Release Artifacts
Write to .claude/specs/<feature-name>/release.md:
## Release: [Feature Name]
### Version
[version bump type] — [rationale]
### Release Date
[current date]
### Changelog
#### User-Facing Changes
- [Change derived from user stories — written for end users]
- [Another change]
#### Technical Changes
- [Change derived from tasks — written for developers]
- [Another change]
#### Breaking Changes
- [Any breaking changes from design.md — with migration path]
### Deployment Checklist
#### Pre-Deployment
- [ ] Database migrations applied: [list specific migrations]
- [ ] Environment variables set: [list with descriptions]
- [ ] External services configured: [list dependencies]
- [ ] Feature flags configured: [if applicable]
- [ ] Rollback plan reviewed
#### Deployment
- [ ] Deploy to staging
- [ ] Run smoke tests on staging (see /spec-verify)
- [ ] Deploy to production
- [ ] Run smoke tests on production
#### Post-Deployment
- [ ] Verify health checks pass
- [ ] Monitor error rates for 30 minutes
- [ ] Notify stakeholders
- [ ] Update documentation (see /spec-docs)
### Environment Variables
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| [VAR_NAME] | Yes/No | [default] | [purpose] |
### Database Migrations
[List of schema changes with migration commands, or "No migrations required"]
### Rollback Plan
[Steps to revert this release if issues are found]
### Contributors
[From git log — authors who committed to this feature]
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.
- 1mo ago First seen · 157 lines · 13 tokens per session scan A a40ad4aa7f56
spec-release is a command published in the GitHub repository Habib0x0/spec-driven-plugin (10 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 1,049 once invoked, about $0.0001 per session on Opus 5.5. 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-31.
Other commands, from other repositories
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
ia-changelog
Create engaging changelogs for recent merges to main branch.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
release
Cut a semver release for the current repo — bump computed from conventional commits, evidence preview, tag + GitHub release.
gh-release
Create a new release for the marketplace or a specific plugin.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.