Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add SteveGJones/ai-first-sdlc-practices/plugin install sdlc-coreWrote 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/stevegjones/ai-first-sdlc-practices/release-plugin)<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/release-plugin"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/release-plugin.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.00022 | $0.00779 |
| Opus 5 | $0.00011 | $0.00390 |
| Sonnet 5 | $0.00004 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
release-plugin 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 8d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Plugin
Package source files into plugin directories based on release-mapping.yaml.
Arguments
patch— Bump patch version (0.1.0 → 0.1.1). Default if no argument.minor— Bump minor version (0.1.0 → 0.2.0).major— Bump major version (0.1.0 → 1.0.0).
Steps
-
Read
release-mapping.yamlfrom the repository root. This file defines which source files map to which plugin directories. -
For each plugin in the mapping, process each component type:
Skills — for each skill entry:
- Read the source file (e.g.,
skills/validate/SKILL.md) - Determine the destination path in the plugin:
plugins/<plugin>/skills/<skill-name>/SKILL.md - The skill directory name comes from the source path (e.g.,
skills/validate/SKILL.md→skills/validate/SKILL.md) - Copy the file, preserving directory structure
- For skills with supporting files (templates, references), copy the entire skill directory
Agents — for each agent entry:
- Read the source file (e.g.,
agents/core/sdlc-enforcer.md) - Copy to
plugins/<plugin>/agents/<filename>
Scripts — for each script entry:
- Read the source file (e.g.,
plugins/sdlc-core/scripts/session-banner.sh) - Copy to
plugins/<plugin>/scripts/<filename> - The validation pipeline itself runs through the
validateskill, not via wrapper scripts. Only hook-invoked scripts (e.g.,session-banner.sh,check-tmp-usage.py) belong here.
Hooks — hooks are plugin-native, no copy needed (they reference
${CLAUDE_PLUGIN_ROOT}) - Read the source file (e.g.,
-
Bump version in each non-stub plugin's
plugin.json:- Read the current version from
.claude-plugin/plugin.json - Apply the version bump (patch/minor/major)
- Write the updated version back
- Also update the version in
.claude-plugin/marketplace.json(at the repo root) for this plugin
- Read the current version from
-
Validate the result:
- Verify every source file in the mapping exists
- Verify every destination file was written
- Check that
plugin.jsonis valid JSON for each plugin - Report any missing source files as errors
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.
- 8d ago First seen · 73 lines · 22 tokens per session scan A d237c37f0ed0
release-plugin is a skill published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 29d ago), licensed MIT. It adds 22 tokens to every session and 779 once invoked, about $0.0001 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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.