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/hamsurang/kit/update-versiongit clone --depth 1 https://github.com/hamsurang/kitWhat 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.00327 |
| Opus 5 | $0.00007 | $0.00163 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
update-version 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 yesterday.
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
Context
- Changed files vs main: !
git diff --name-only origin/main...HEAD - Current marketplace.json: !
cat .claude-plugin/marketplace.json
Your task
-
Find changed plugins Parse the changed files list. For each unique
plugins/<name>/directory, that plugin needs a version bump. -
For each changed plugin:
- Read
plugins/<name>/.claude-plugin/plugin.json - Get the diff for that plugin:
git diff origin/main...HEAD -- plugins/<name>/ - Determine bump type:
major: skill or command file removed/renamed, breaking behavior changeminor: new command, skill, or agent file addedpatch: content edits, docs, bug fixes, refactoring
- Bump
versioninplugin.jsonusing semver (e.g. 1.0.0 → 1.0.1 for patch)
- Read
-
Bump marketplace version in
.claude-plugin/marketplace.json:- Take the highest bump type across all changed plugins
- Apply that bump to the current marketplace
versionfield
-
Report all changes: list each plugin and old→new version, and marketplace old→new version.
Do NOT commit. Only update the JSON files.
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.
- yesterday First seen · 32 lines · 14 tokens per session scan A 43f5d45d5c61
update-version is a command published in the GitHub repository hamsurang/kit (19 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 327 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.