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 skills/pangon/ai-sdlc-framework/sdlc-releasenpx skills add pangon/ai-sdlc-framework --skill sdlc-releasegit clone --depth 1 https://github.com/pangon/ai-sdlc-frameworkWrote 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/pangon/ai-sdlc-framework/sdlc-release)<a href="https://agentmods.dev/skills/pangon/ai-sdlc-framework/sdlc-release"><img src="https://agentmods.dev/badge/skills/pangon/ai-sdlc-framework/sdlc-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.1 | $0.00069 | $0.01027 |
| Opus 5 | $0.00034 | $0.00513 |
| Sonnet 5 | $0.00014 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00103 |
Grade A, and why
SDLC-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 6d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
You are releasing a new version of the AI SDLC Framework from its own repository. A release consists of: a finalized changelog entry, the version stamp updated in FRAMEWORK.md, a release commit, and a v<version> tag on that commit.
Scope guard
This skill applies only to the framework repository. Before doing anything, verify:
CHANGELOG.mdandRATIONALE.mdexist, andREADME.mdis titled "AI SDLC Framework".**Phase**:in the Current State section ofCLAUDE.mdisNot initialized.
If any check fails, you are most likely inside an instantiated project where the Quick Start rm step was skipped: stop, explain this, and suggest removing .claude/skills/SDLC-release/ (and any other leftover Upstream-only files) instead of releasing.
Versioning semantics
The framework uses Semantic Versioning, interpreted for a process framework:
- MAJOR — changes that require migration of existing instantiated-project content, or that break compatibility of the procedures: artifact or index format changes, Current State Protocol changes, ID-scheme changes, manifest recategorizations that move ownership of existing files, removal or renaming of skills.
- MINOR — backward-compatible framework changes: new skills, new templates, new or expanded procedures and instructions that existing project content satisfies as-is.
- PATCH — fixes and clarifications with no behavioral change to project content: wording, typos, corrections of procedure bugs that do not alter any format.
Versions only increase; a published tag is never moved or reused.
Changelog conventions
CHANGELOG.md follows Keep a Changelog: an ## [Unreleased] section accumulates entries as framework changes land (every framework change should add its entry there in the same operation), and releasing converts it into a dated version section. When a release requires action in instantiated projects (any MAJOR, occasionally a MINOR), its entry must include a ### Migration subsection stating what a project on the previous version must do.
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.
- 6d ago First seen · 51 lines · 69 tokens per session scan A 5f365549035e
SDLC-release is a skill published in the GitHub repository pangon/ai-sdlc-framework (125 stars, last pushed 13d ago), licensed Apache-2.0. It adds 69 tokens to every session and 1,027 once invoked, about $0.0003 per session on Opus 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-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…