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 skills/goodeye-labs/goodeye-cli/bump-versionnpx skills add Goodeye-Labs/goodeye-cli --skill bump-versiongit clone --depth 1 https://github.com/Goodeye-Labs/goodeye-cliWrote 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/skills/goodeye-labs/goodeye-cli/bump-version)<a href="https://agentmods.dev/skills/goodeye-labs/goodeye-cli/bump-version"><img src="https://agentmods.dev/badge/skills/goodeye-labs/goodeye-cli/bump-version.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.00517 |
| Opus 5 | $0.00019 | $0.00259 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
bump-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 4d 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
goodeye-cli Version Bump
Two phases: (1) bump commit, always; (2) tag + push, only on explicit instruction.
Step 1: Determine new version
User override always wins. Accept any of:
- Bump type:
major,minor,patch - Explicit target:
bump to 1.0.0 - Pre-release (PEP 440):
0.9.0a1,0.9.0rc1
Without override, inspect commits since the last tag:
git describe --tags --abbrev=0 # last tag, e.g. v0.8.0
git log <last-tag>..HEAD --oneline # commits to classify
SemVer rules:
- major: breaking change, removed/renamed command, incompatible flag change
- minor: new subcommand, new flag, new user-visible feature
- patch: bug fix, internal refactor, docs, CI, dependency update, chore
Bias toward patch over minor, minor over major when ambiguous.
Step 2: Edit files
pyproject.toml: one line change:
version = "X.Y.Z"
uv.lock: run from repo root after editing pyproject.toml:
uv lock
Updates only the self-referential [[package]] name = "goodeye" entry. No dependency upgrades occur.
Step 3: Commit
Stage exactly these two files:
git add pyproject.toml uv.lock
Commit message (no body):
chore: bump version to X.Y.Z
Step 4: Tag and push (explicit instruction only)
Only proceed if the user explicitly says to tag, push, release, or publish (e.g. "tag it", "push the tag", "ship it to PyPI").
Verify the tag doesn't already exist, then:
git tag vX.Y.Z
git push origin vX.Y.Z
This triggers publish.yml -> builds wheel -> publishes to PyPI via OIDC trusted publishing. No manual credentials needed. Monitor at github.com/Goodeye-Labs/goodeye-cli/actions.
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.
- 4d ago First seen · 67 lines · 39 tokens per session scan A 637e0e4c8b48
bump-version is a skill published in the GitHub repository Goodeye-Labs/goodeye-cli (4 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 517 once invoked, about $0.0002 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 skills, from other repositories
render-release-notes
Render release notes to HTML and check the rendered output in a browser.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…