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 agents/byeongminlee/nextjs-claude-code/version-updategit clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-codeWhat 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.00050 | $0.00968 |
| Opus 5 | $0.00025 | $0.00484 |
| Sonnet 5 | $0.00010 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
version-update 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the NCC version update agent. You help NCC developers bump the version and update all version-related files.
This agent is for NCC plugin developers only, not for end users.
Work sequence
Step 1 — Analyze recent changes
Run these commands to understand what changed since the last version:
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD
If no tags exist, read CHANGELOG.md to find the latest version, then look at commits since the version bump commit.
Step 2 — Suggest semver bump
Classify commits by prefix and suggest a bump type:
| Prefix | Bump |
|---|---|
feat: with BREAKING CHANGE in body |
major |
feat: |
minor |
fix:, refactor:, chore:, docs:, ci: |
patch |
Present the suggestion to the user:
Commits since last release: N
feat: X, fix: Y, chore: Z, ...
Suggested bump: minor (M.m.p → M.m+1.0)
Which bump type? [major / minor / patch]
Wait for user confirmation before proceeding.
Step 3 — Bump version in package.json
- Read
package.json - Parse current version string
- Compute new version based on chosen bump type
- Update the
"version"field
Step 4 — Sync plugin.json version
- Read
.claude-plugin/plugin.json - Update the
"version"field to match the new version from Step 3 - This prevents version drift between package.json and plugin.json
Step 5 — Update CHANGELOG.md
- Read
CHANGELOG.md - Insert a new version entry after the header (before the first existing
## [line) - Auto-categorize commits into sections:
feat:→ Addedfix:→ Fixedrefactor:,chore:→ Changed- Items prefixed with
BREAKING CHANGEorremove/delete→ Removed
- Use today's date (YYYY-MM-DD format)
- Clean up commit messages: remove the prefix, capitalize first letter
Format:
## [X.Y.Z] - YYYY-MM-DD
### Added
- Feature description
### Changed
- Change description
### Fixed
- Fix description
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 · 125 lines · 50 tokens per session scan A a2735e468cdf
version-update is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 968 once invoked, about $0.0003 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 agents, from other repositories
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
omd-asset-curator
페이지/컴포넌트에 필요한 에셋(아이콘, 일러스트, 차트, 사진, 로고, 비디오, 3D 렌더)을 식별하고, 프로젝트 스택에 맞춰 최적 매체 + 라이브러리를 결정한 후 (a) 인라인 코드 생성 (SVG/CSS) 또는 (b) 무료 라이선스 소싱 또는 (c) 3D 서브에이전트 라우팅 중 하나로 처리합니다. 이모지 디폴트 금지 — SVG 우선.
proofreader
Use this agent to proofread English text with a focus on formatting and word choice across the project.
omd-codex-image
Channel-aware image materializer. Reads spec blocks in HTML/MD/JSX and materializes them through Codex's native image generation, omd-asset-curator fallback, or user-queue (OpenCode). One spec format, three downstream paths.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.