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 zenml-io/kitaru-skills --skill skills-releasegit clone --depth 1 https://github.com/zenml-io/kitaru-skillsWrote 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/zenml-io/kitaru-skills/skills-release)<a href="https://agentmods.dev/skills/zenml-io/kitaru-skills/skills-release"><img src="https://agentmods.dev/badge/skills/zenml-io/kitaru-skills/skills-release/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/zenml-io/kitaru-skills/skills-release"><img src="https://agentmods.dev/badge/skills/zenml-io/kitaru-skills/skills-release.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.00047 | $0.00923 |
| Opus 5 | $0.00023 | $0.00462 |
| Sonnet 5 | $0.00009 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
skills-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 11d 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.
This is a copy
100% identical to skills-release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Release
Overview
main is the distribution branch: /plugin marketplace add zenml-io/kitaru-skills
installs whatever main holds, immediately. develop is the working base. A
release moves main forward to develop's current commit as a fast-forward
and stamps a plugin version, so main is always an exact snapshot of
develop at release time.
The main-release-only ruleset blocks all pushes and PR merges to main
except by repository admins. A release is therefore an admin running this
checklist — never a PR into main, never a force push.
Versions are this repository's own plugin versions. Do not reuse Kitaru product version numbers; state tested Kitaru compatibility in the release notes instead.
Preconditions
Stop and resolve before releasing if any of these fail:
- On
developwith a clean working tree. git fetch origindone; localdevelopin sync withorigin/develop.- Fast-forward is possible:
git merge-base --is-ancestor origin/main origin/developexits 0. A non-zero exit meansmainhas commitsdeveloplacks — investigate how they got there; never force-push over them.
Steps
-
Review what ships:
git log --oneline origin/main..origin/develop. Draft release notes from these commits (what changed, why it matters to installers), plus a "Tested against Kitaru X.Y" line when known. -
Agree the next version with the user: minor for new or changed skills, patch for fixes and docs-only changes.
-
Bump all three version fields to the same value:
.claude-plugin/plugin.json→.version.claude-plugin/marketplace.json→.metadata.version.claude-plugin/marketplace.json→.plugins[0].version
-
Validate:
jq . .claude-plugin/plugin.jsonandjq . .claude-plugin/marketplace.jsonparse, and all three fields match:jq -r .version .claude-plugin/plugin.json jq -r '.metadata.version, .plugins[0].version' .claude-plugin/marketplace.json -
Commit only the two JSON files on
developwith subjectRelease vX.Y.Z, then pushdevelop. -
Tag the release commit:
git tag vX.Y.Z && git push origin vX.Y.Z. -
Fast-forward
main:git push origin develop:main. No--forceever — a rejection means the push is not a fast-forward; go back to Preconditions. -
Publish the drafted notes via a file, never inline in the command — commit subjects routinely contain backticks, which the shell would execute as command substitution inside a
--notes "..."argument. Write the notes to a scratch file with a file-writing tool (or a quoted heredoc,cat > notes.md <<'EOF'), then:
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.
- 11d ago First seen · 87 lines · 47 tokens per session scan A 3b20281fdcd7
skills-release is a skill published in the GitHub repository zenml-io/kitaru-skills (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 923 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to skills-release, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
skill-ship
Package and finalize completed work for delivery — use when a feature is done and ready to ship.
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).