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/lukasrepublic/agentic-foundry/cut-releasenpx skills add lukasrepublic/agentic-foundry --skill cut-releasegit clone --depth 1 https://github.com/lukasrepublic/agentic-foundryWrote 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/lukasrepublic/agentic-foundry/cut-release)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/cut-release"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/cut-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 | $0.00165 | $0.06063 |
| Opus 5 | $0.00082 | $0.03031 |
| Sonnet 5 | $0.00033 | $0.01213 |
| Haiku 4.5 | $0.00016 | $0.00606 |
Grade A, and why
cut-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 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/foundry:cut-release — the cut-release playbook
The FIRST foundry playbook (a guarded, looping skill — task-triggered, loop held by an
EXIT GATE, floors orthogonal; see docs/TERMINOLOGY.md). It turns the release-cut procedure — which lived only as memory-prose
and was hand-run ~6× (every recurring gotcha was that procedure failing) — into a self-contained,
gated loop driven by scripts/foundry-cut-release.py.
Its EXIT GATE is the EXISTING acceptance verdict (foundry-release-acceptance.run_acceptance) — the
only gate this script invokes; it reimplements no gate logic. The closure derivation
(foundry_release.py) is upstream prep the operator runs before the cut, not invoked here. It
adds no new floor and never runs git tag / git push — it emits the publish plan as
data and the operator executes it.
Retired: the wiring-pin migrate. This loop once named a
foundry-wiring-hash.pywiring-pin migrate step, re-checked transitively via DOCTOR-GREEN. That mechanism —scripts/foundry-wiring-hash.py, the.foundry/wiring-hash.pinfile, and the doctor's wiring-hash check — was retired; the currentfoundry-doctor.py(a thin 5-check probe,skills/doctor/SKILL.md) carries no wiring-hash check to re-check. What carries the load today is thefoundry-release-acceptancegate (run_acceptance) this loop's EXIT GATE already calls. Seeskills/release/SKILL.md's "Gate-wiring pin & manifest" tombstone for the fuller history.
The playbook shape (the standard template — see docs/TERMINOLOGY.md §6)
- TRIGGER — the operator is cutting/shipping a release (description-matched; no global pointer).
- ENGINE —
deterministic-seam-drive: ordered prep-check → machine gate → emit plan. - EXIT GATE —
foundry-release-acceptance.py run_acceptance(tree) == pass(the artifact-sha-bound verdict). The loop is NOT "done" until the gate is green; nothing reaches tag/push before that. - FLOORS TOUCHED — none new. The orthogonal floors (front-authorization, the per-atom merge floor, the acceptance HARD-STOP) already fired upstream; cut-release only sequences and refuses-until-green. It never folds a floor into a step.
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 · 318 lines · 165 tokens per session scan A cfae82902e1a
cut-release is a skill published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed 3d ago), licensed MIT. It adds 165 tokens to every session and 6,063 once invoked, about $0.0008 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
changelog
Auto-generate changelog from git commits — grouped by feat/fix/docs with PR links.
commit
Create a commit following repository guidelines with proper versioning and changelog updates.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
draft-release-notes
Turn changelog-scan output into polished, categorized release notes draft. Propose only.