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 skills add zircote-plugins/sdlc-quality --skill releasegit clone --depth 1 https://github.com/zircote-plugins/sdlc-qualityWrote 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/skills/zircote-plugins/sdlc-quality/release)<a href="https://agentmods.dev/skills/zircote-plugins/sdlc-quality/release"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/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/skills/zircote-plugins/sdlc-quality/release"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/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.00063 | $0.01647 |
| Opus 5.5 | $0.00025 | $0.00659 |
| Sonnet 5.5 | $0.00013 | $0.00329 |
| Haiku 4.5 | $0.00006 | $0.00165 |
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 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Management Standards
Guidance for implementing release requirements including versioning, automation, and publishing workflows.
Tooling
Available Tools: If using Claude Code, the
agents:releaseskill can prepare and execute releases with version bumps and validation. Thedocumentation-review:changelogskill manages changelog entries.
Versioning Requirements
Semantic Versioning (MUST)
Projects MUST follow Semantic Versioning (SemVer):
MAJOR.MINOR.PATCH[-PRERELEASE][+BUILD]
| Component | When to Increment |
|---|---|
| MAJOR | Breaking API changes |
| MINOR | New backwards-compatible features |
| PATCH | Backwards-compatible bug fixes |
| PRERELEASE | Pre-release versions (alpha, beta, rc) |
| BUILD | Build metadata (ignored for precedence) |
Version Examples
1.0.0 # Initial release
1.0.1 # Patch release (bug fix)
1.1.0 # Minor release (new feature)
2.0.0 # Major release (breaking change)
2.0.0-alpha.1 # Pre-release
2.0.0-rc.1 # Release candidate
2.0.0+build.123 # With build metadata
Pre-release Versions (MUST)
Pre-release versions MUST follow this progression:
x.y.z-alpha.N- Early testing, unstablex.y.z-beta.N- Feature complete, testingx.y.z-rc.N- Release candidate, final testing
Release Process
Pre-Release Checklist (MUST)
Before releasing, verify:
| Check | Requirement |
|---|---|
| All tests pass | MUST |
| No security vulnerabilities | MUST |
| Documentation updated | MUST |
| CHANGELOG updated | MUST |
| Version bumped | MUST |
| Breaking changes documented | MUST (if applicable) |
| Migration guide provided | SHOULD (for major versions) |
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 · 283 lines · 63 tokens per session scan A be66b052b814
release is a skill published in the GitHub repository zircote-plugins/sdlc-quality (11 stars, last pushed 22d ago), licensed MIT. It adds 63 tokens to every session and 1,647 once invoked, about $0.0003 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 skills, from other repositories
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
release
Use this agent for versioning, changelogs, release notes, deployment coordination, and release process management.
deployment-safety
Production deployment rules, rollback-first recovery, dependency batching, CI cost awareness, framework upgrade verification, fallback observability, and GitHub repo settings standardization.
cli-forge-github
Audit and fix GitHub repository health: rulesets vs CI alignment, branch hygiene, PR lifecycle, release automation flow, permission issues, and transient CI failures. Detects misconfigurations that cause PRs to hang, CI to fail silently, branches to accumulate, and releases to stall. Use when the user says 'PR stuck'…