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/qwickapps/ai-sdlc-workflowsWrote 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/qwickapps/ai-sdlc-workflows/release)<a href="https://agentmods.dev/commands/qwickapps/ai-sdlc-workflows/release"><img src="https://agentmods.dev/badge/commands/qwickapps/ai-sdlc-workflows/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/qwickapps/ai-sdlc-workflows/release"><img src="https://agentmods.dev/badge/commands/qwickapps/ai-sdlc-workflows/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.00004 | $0.00660 |
| Opus 5.5 | $0.00002 | $0.00264 |
| Sonnet 5.5 | $0.00001 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
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 2mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Management Workflow
You are now in Release Mode. Follow this workflow for version releases.
Input: $ARGUMENTS (version number like 1.2.0, or "patch"/"minor"/"major")
CRITICAL RULES
- Coordinate all aspects - code, docs, deployment
- NEVER auto-push - always wait for explicit approval
- No attributions in commit messages or release notes
Interactive Setup
Check if $ARGUMENTS is provided.
If $ARGUMENTS is empty, ask:
"What version would you like to release? Please provide:
- Version number (e.g., 1.2.0) or type (patch/minor/major)
- Confirm what features/fixes are included
- Any special release notes needed"
Wait for response before proceeding.
Workflow Phases
PHASE 1: Release Planning (Engineering Manager)
-
Define release scope:
- What version number? (semver)
- What features/fixes are included?
- Any breaking changes?
- What needs documentation?
-
Pre-release checklist:
- All features merged and tested
- All tests passing
- No critical bugs outstanding
- Documentation updated
-
GATE: Confirm release scope with user
PHASE 2: Prepare Release (DevOps + Tech Writer)
-
Update version numbers:
- package.json (if applicable)
- Other version references
-
Finalize CHANGELOG.md:
- Add release date
- Organize entries by category
- Note breaking changes prominently
-
Update documentation:
- README.md - version badges, new features
- ARCHITECTURE.md - if architecture changed
- Migration guide if breaking changes
-
Create Release Document:
- Save to:
.claude/engineering/releases/RELEASE-<version>.md - Use template from
.claude/templates/RELEASE.md
- Save to:
-
GATE: Present release preparation to user
PHASE 3: Create Release (DevOps)
-
Commit release changes:
chore(release): v<version> - list of notable changes -
Create git tag (if requested)
-
GATE: Wait for user approval before pushing
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.
- 2mo ago First seen · 101 lines · 4 tokens per session scan A d3a8ab70b252
release is a command published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 7mo ago), licensed MIT. It adds 4 tokens to every session and 660 once invoked, about $0.0000 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
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.