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 commands/kubb-labs/kubb/changesetgit clone --depth 1 https://github.com/kubb-labs/kubbWhat 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.00014 | $0.00158 |
| Opus 5 | $0.00007 | $0.00079 |
| Sonnet 5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
changeset 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 2d 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
!git diff --stat HEAD
Create a Changeset for the changes above.
- Determine which workspace packages are affected.
- Choose the bump type from
$ARGUMENTS(defaultpatchwhen empty):patchfor fixes,minorfor backwards-compatible features,majorfor breaking changes. - Add a markdown file under
.changeset/with the correct frontmatter and a concise, user-facing summary of what changed and why.
For wording and release-note conventions, follow the changelog skill. For the surrounding
PR checklist, follow the pr skill.
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.
- 2d ago First seen · 18 lines · 14 tokens per session scan A b86ab9baf425
changeset is a command published in the GitHub repository kubb-labs/kubb (1,788 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 158 once invoked, about $0.0001 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-30.
Other commands, from other repositories
skmtc-retro-review
Aggregate SKMTC friction log entries into a review — cluster patterns, classify interventions, calculate convergence metrics, produce an action plan.
skmtc-retro
Run a SKMTC retrospective on the current session — capture friction and wins to the friction log.
CLAUDE
Command "CLAUDE" from skmtc/skmtc, covering recent activity, may 5, 2026, may 8, 2026, may 9, 2026 and may 11, 2026.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.