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/bugzy-ai/bugzy/publishgit clone --depth 1 https://github.com/bugzy-ai/bugzyWhat 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.00015 | $0.00237 |
| Opus 5 | $0.00008 | $0.00118 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
publish 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
Publish Command
This command handles the complete release process for the bugzy package.
Additional instructions: $ARGUMENTS
What it does:
- Determines the version bump type (patch, minor, major) based on changes
- Updates version in package.json using
npm version patch|minor|major --no-git-tag-version - Builds the package using
pnpm build - Publishes to GitHub Packages using
node scripts/publish.js - Commits the changes
- Pushes to the remote repository
IMPORTANT: Publishing to GitHub Packages
Do NOT use npm publish directly. Always use the custom publish script:
node scripts/publish.js
This script:
- Loads
GITHUB_TOKENfrom.env.localor.env - Validates the token is present
- Runs
pnpm publish --no-git-checks
Prerequisites:
- Ensure
GITHUB_TOKENis set in.envor.env.local
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 · 34 lines · 15 tokens per session scan A 11e08bc5f645
publish is a command published in the GitHub repository bugzy-ai/bugzy (5 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 237 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-31.
Other commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.