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/ghostlygawd/engineering-board/release-engineering-boardnpx skills add GhostlyGawd/engineering-board --skill release-engineering-boardgit clone --depth 1 https://github.com/GhostlyGawd/engineering-boardWrote 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/ghostlygawd/engineering-board/release-engineering-board)<a href="https://agentmods.dev/skills/ghostlygawd/engineering-board/release-engineering-board"><img src="https://agentmods.dev/badge/skills/ghostlygawd/engineering-board/release-engineering-board.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 | $0.00073 | $0.00735 |
| Opus 5 | $0.00036 | $0.00367 |
| Sonnet 5 | $0.00015 | $0.00147 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
release-engineering-board 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Engineering Board
Use this skill only in the GhostlyGawd/engineering-board source repository.
Do not use it in a repository that only installs the Engineering Board plugin.
Use the repository script for release preparation. Do not update release files independently.
Prepare the release
-
Read
docs/RELEASING.md. -
Confirm that the release branch is clean.
-
Confirm that the Codex manifest, Claude manifest, marketplace, Python package, MCP manifests, README badge, architecture release line, product release boundary, and security support line have the current version.
-
Select the next Semantic Versioning value from the
[Unreleased]changes. -
Preview the coordinated change:
python3 scripts/prepare-release.py <version> -
Review every listed file, including the current-truth documentation, and the prospective MCP bundle checksum.
-
Apply the same plan:
python3 scripts/prepare-release.py <version> --apply -
Run the complete test suite:
bash tests/run-all.sh -
From a host with Claude Code installed, validate the prepared Claude marketplace with warnings treated as errors:
claude plugin validate --strict .Stop if the validator is unavailable, reports a warning, or exits nonzero. Keep this host-native release gate separate from the dependency-free CI toolchain.
-
Commit and push the release-preparation change.
If approved review changes modify the prepared bundle, use --refresh with
the current prepared version. Preview the refresh before you apply it. Refresh
must not create another changelog section. Do not use refresh to change the
target version.
Publish the release
Publish only from a commit on main. Do not move an existing tag.
Use .github/workflows/release.yml with:
- the exact
v<version>tag; - the exact
maincommit; - MCP Registry publication when the release must update that registry;
- PyPI publication when the release must update that package.
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.
- 4d ago First seen · 100 lines · 73 tokens per session scan A ed022cde59d1
release-engineering-board is a skill published in the GitHub repository GhostlyGawd/engineering-board (0 stars, last pushed 5d ago), licensed MIT. It adds 73 tokens to every session and 735 once invoked, about $0.0004 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-31.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
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…