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 skills add amergrgic/kodama --skill project-release-checkgit clone --depth 1 https://github.com/amergrgic/kodamaWrote 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/amergrgic/kodama/project-release-check)<a href="https://agentmods.dev/skills/amergrgic/kodama/project-release-check"><img src="https://agentmods.dev/badge/skills/amergrgic/kodama/project-release-check/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/amergrgic/kodama/project-release-check"><img src="https://agentmods.dev/badge/skills/amergrgic/kodama/project-release-check.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00092 |
| Opus 5.5 | $0.00007 | $0.00037 |
| Sonnet 5.5 | $0.00004 | $0.00018 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
project-release-check 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 1mo 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
Project release check
- Run the test and lint commands from
AGENTS.md. - Confirm generated files are current and no generated file was manually edited.
- Review public API changes for backwards compatibility.
- Verify release notes describe user-visible changes.
Report the exact commands run and any checks that could not be completed.
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.
- 1mo ago First seen · 14 lines · 18 tokens per session scan A 713b0d1636d3
project-release-check is a skill published in the GitHub repository amergrgic/kodama (11 stars, last pushed 16d ago), licensed MIT. It adds 18 tokens to every session and 92 once invoked, about $0.0001 per session on Opus 5.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
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.
github-repo-management
Clone, create, fork repos; manage remotes, releases.
akiship
Full release ritual end-to-end — front-loaded checks, then an unattended pass. ACTIVATION = the literal token /akiship, or an imperative turn, in any language, ordering the release ritual for this repo. A question about it, or a completion word with no release object, activates nothing — consult the checklist and…
deploy-pipeline-runbook
Use when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt state in a downstream system.
secret-leak-preflight
Use when about to commit, push, or publish -- staged changes touch config or environment files, generated artifacts (relay sessions, logs, build output) are being added, or the session handled credentials even indirectly.
pre-release-verification
Use when a release candidate needs final checks before tagging, publishing, or production deployment.