Zoo Code is a code-editor extension that provides a team of AI agents for software development. Developers use it for coding assistance, code search, task coordination, and autonomous work, while the catalogue entries extend its workflows.
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.
git clone --depth 1 https://github.com/Zoo-Code-Org/Zoo-CodeWrote 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/commands/zoo-code-org/zoo-code/cli-release)<a href="https://agentmods.dev/commands/zoo-code-org/zoo-code/cli-release"><img src="https://agentmods.dev/badge/commands/zoo-code-org/zoo-code/cli-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/commands/zoo-code-org/zoo-code/cli-release"><img src="https://agentmods.dev/badge/commands/zoo-code-org/zoo-code/cli-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.00009 | $0.00635 |
| Opus 5.5 | $0.00004 | $0.00254 |
| Sonnet 5.5 | $0.00002 | $0.00127 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
cli-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 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.
This is a copy
100% identical to cli-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.
What it actually says
-
Identify changes since the last CLI release:
- Get the last CLI release tag:
gh release list --limit 10 | grep "cli-v" - View changes since last release:
git log cli-v<last-version>..HEAD -- apps/cli --oneline - Or for uncommitted changes:
git diff --stat -- apps/cli
- Get the last CLI release tag:
-
Review and summarize the changes to determine an appropriate changelog entry. Group changes by type:
- Added: New features
- Changed: Changes to existing functionality
- Fixed: Bug fixes
- Removed: Removed features
- Tests: New or updated tests
-
Bump the version in
apps/cli/package.json:- Increment the patch version (e.g., 0.0.43 → 0.0.44) for bug fixes and minor changes
- Increment the minor version (e.g., 0.0.43 → 0.1.0) for new features
- Increment the major version (e.g., 0.0.43 → 1.0.0) for breaking changes
-
Update
apps/cli/CHANGELOG.mdwith a new entry:- Add a new section at the top (below the header) following this format:
## [X.Y.Z] - YYYY-MM-DD ### Added - Description of new features ### Changed - Description of changes ### Fixed - Description of bug fixes- Use the current date in YYYY-MM-DD format
- Include links to relevant source files where helpful
- Describe changes from the user's perspective
-
Create a release branch and commit the changes:
# Ensure you're on main and up to date git checkout main git pull origin main # Create a new branch for the release git checkout -b cli-release-v<version> # Commit the version bump and changelog update git add apps/cli/package.json apps/cli/CHANGELOG.md git commit -m "chore(cli): prepare release v<version>" # Push the branch to origin git push -u origin cli-release-v<version> -
Create a pull request for the release:
gh pr create --title "chore(cli): prepare release v<version>" \ --body "## CLI Release v<version> This PR prepares the CLI release v<version>. ### Changes - Version bump in package.json - Changelog update ### Checklist - [ ] Version number is correct - [ ] Changelog entry is complete and accurate - [ ] All CI checks pass" \ --base main
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 · 87 lines · 9 tokens per session scan A 2539c89c2141
cli-release is a command published in the GitHub repository Zoo-Code-Org/Zoo-Code (2,014 stars, last pushed today), licensed Apache-2.0. It adds 9 tokens to every session and 635 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cli-release, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.