Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/SienkLogic/plan-build-runnpx agentmods add skills/sienklogic/plan-build-run/releaseWrote 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/sienklogic/plan-build-run/release)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/release"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/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.00014 | $0.01657 |
| Opus 5 | $0.00007 | $0.00829 |
| Sonnet 5 | $0.00003 | $0.00331 |
| Haiku 4.5 | $0.00001 | $0.00166 |
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 2d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes tokens. Begin executing Step 1 immediately.
Step 0 — Immediate Output
Before ANY tool calls, display this banner:
╔══════════════════════════════════════════════════════════════╗
║ PLAN-BUILD-RUN ► RELEASE ║
╚══════════════════════════════════════════════════════════════╝
Then proceed to Step 1.
/pbr:release — Changelog & Release Notes
You are running the release skill. This skill generates polished, user-facing changelog entries from project history — milestone summaries, commit logs, and planning artifacts. It produces Keep a Changelog format with bolded feature names and impact-focused descriptions.
This skill runs inline (no subagents).
Argument Parsing
Parse $ARGUMENTS:
$ARGUMENTS format: [version] [--flag]
Examples:
"" → mode=draft, version=auto-detect from package.json
"v2.2.0" → mode=draft, version=v2.2.0
"--draft" → mode=draft, version=auto-detect
"--update v2.1.0" → mode=update, version=v2.1.0
"--clean" → mode=clean, run clean-changelog.js on existing CHANGELOG.md
Modes:
draft(default) — Generate a new changelog entry for unreleased workupdate— Regenerate the entry for an existing versionclean— Run the scope-cleaning script on the current CHANGELOG.md
Mode: clean
Run the changelog cleaning script to strip internal scopes from existing entries:
node scripts/clean-changelog.js --write
Display the result and exit.
Mode: draft or update
Step 1 — Gather Context
-
Determine version:
- If provided: use it (auto-prefix
vif missing) - If not: read
package.jsonversion field and use that
- If provided: use it (auto-prefix
-
Read current CHANGELOG.md (if exists):
- Parse existing version entries to avoid duplicating
- If
updatemode: find the section for the target version to replace
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.
- 2d ago First seen · 207 lines · 14 tokens per session scan A dd654df88d18
release is a skill published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 1,657 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-09-03.
Other skills, from other repositories
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
source-command-update-infos-release
Update Codex releases tracking (guide + landing + version bump).
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.
talk-stage2-research
Performs git archaeology, changelog analysis, and builds a verified factual timeline by cross-referencing git history with source material. REX mode only (skipped automatically in Concept mode). Use when building a REX talk and you need verified commit metrics, release timelines, and contributor data from a git…