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/mtvrkan/senior-dev-kit/release-gatenpx skills add mtvrkan/senior-dev-kit --skill release-gategit clone --depth 1 https://github.com/mtvrkan/senior-dev-kitWrote 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/mtvrkan/senior-dev-kit/release-gate)<a href="https://agentmods.dev/skills/mtvrkan/senior-dev-kit/release-gate"><img src="https://agentmods.dev/badge/skills/mtvrkan/senior-dev-kit/release-gate.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.00040 | $0.00363 |
| Opus 5 | $0.00020 | $0.00181 |
| Sonnet 5 | $0.00008 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
release-gate 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.
What it actually says
release-gate
Release safety check for: $ARGUMENTS. Output GO / NO-GO per item:
- BUILD: clean build with no errors?
- TESTS: all passing? Any skipped/flaky tests that matter?
- MIGRATIONS: pending? If yes and not yet reviewed, run
migration-reviewfirst — this item only confirms that review happened, it doesn't replace it. - ENV/CONFIG: new vars required? Documented and configured in all environments?
- SECURITY: auth/payment/secrets changes present? If
security-scanhasn't run yet for this release, run it first — this item confirms it completed and findings were addressed, it doesn't replace it. - BACKWARD COMPAT: breaking API, schema, or behavior changes affecting consumers?
- ROLLBACK PLAN: how to revert if this release fails?
- KNOWN RISKS: anything uncertain or untested?
- SBOM: generated and scanned for this release (devops-guard has the commands)? If missing, flag as blocker.
Final: GO / NO-GO | summary | blockers list | recommended next step Do not deploy. Do not run migrations. Report only.
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 · 28 lines · 40 tokens per session scan A 6a4bf3597d95
release-gate is a skill published in the GitHub repository mtvrkan/senior-dev-kit (5 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 363 once invoked, about $0.0002 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…