Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/gopherguides/gopher-ainpx agentmods add commands/gopherguides/gopher-ai/releaseWrote 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/gopherguides/gopher-ai/release)<a href="https://agentmods.dev/commands/gopherguides/gopher-ai/release"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/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/gopherguides/gopher-ai/release"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/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.00015 | $0.03388 |
| Opus 5.5 | $0.00006 | $0.01355 |
| Sonnet 5.5 | $0.00003 | $0.00678 |
| Haiku 4.5 | $0.00002 | $0.00339 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Repository: !
basename \git rev-parse --show-toplevel 2>/dev/null` 2>/dev/null || echo "unknown"` - Current version: !
jq -r '.plugins[0].version' .claude-plugin/marketplace.json 2>/dev/null || echo "unknown" - Latest tag: !
git describe --tags --abbrev=0 2>/dev/null || echo "No tags found" - Commits since last tag: !
TAG=\git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD`; git log "$TAG"..HEAD --oneline 2>/dev/null | wc -l | tr -d ' ' || echo "0"`
Instructions
Create a new release for the gopher-ai plugin marketplace.
Bump Type
If $ARGUMENTS is provided (patch, minor, or major), use that bump type.
If $ARGUMENTS is empty, analyze commits since the last tag to suggest a bump type:
- major: Any breaking changes (
BREAKING CHANGE:,!:suffix) - minor: Any new features (
feat:) - patch: Bug fixes and other changes (
fix:,chore:,docs:, etc.)
Ask the user to confirm the bump type using AskUserQuestion before proceeding.
Workflow
-
Validate State
- Ensure working directory is clean:
git status --porcelain - Ensure we're on the main branch
- Fetch
origin/mainand requireHEADto equalorigin/main - Ensure no uncommitted changes
- Ensure working directory is clean:
-
Detect Changelog Strategy
Automatically detect whether the project uses PR-based or direct-commit workflow:
# Get last tag (or first commit if no tags) LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD) # Count total commits since last tag TOTAL_COMMITS=$(git log "$LAST_TAG"..HEAD --oneline | wc -l | tr -d ' ') # Count commits with PR references like (#123) PR_COMMITS=$(git log "$LAST_TAG"..HEAD --oneline | awk '/\(#[0-9]+\)/ { count++ } END { print count+0 }') # Calculate percentage (avoid division by zero) if [ "$TOTAL_COMMITS" -gt 0 ]; then PR_PERCENTAGE=$((PR_COMMITS * 100 / TOTAL_COMMITS)) else PR_PERCENTAGE=0 fi
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 · 277 lines · 15 tokens per session scan A f7c6fd2a91f5
release is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 3,388 once invoked, about $0.0001 per session on Opus 5.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-09-03.
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.
ship
Ship is the operational release-prep flow for a connected project repo.