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 skills add hoangsonww/Claude-Code-Agent-Monitor --skill version-releasegit clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-MonitorWrote 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/hoangsonww/claude-code-agent-monitor/version-release)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/version-release"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/version-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/skills/hoangsonww/claude-code-agent-monitor/version-release"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/version-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.01402 |
| Opus 5 | $0.00025 | $0.00701 |
| Sonnet 5 | $0.00010 | $0.00280 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
version-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 12d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Release Skill
Apply Semantic Versioning across CCAM:
- Patch (
X.Y.Z+1): backward-compatible fixes, docs-only work, dependency/security maintenance, refactors, or small improvements without a substantial new capability. - Minor (
X.Y+1.0): backward-compatible features or meaningfully larger capabilities such as new workflows, pages, integrations, API fields/routes, or major UX surfaces. - Major (
X+1.0.0): breaking public behavior, removed or renamed contracts, required migrations, or fundamental product/architecture changes.
Choose the highest applicable category. If the boundary is ambiguous, prefer the higher bump or ask before release. Do not classify from diff size or commit count alone. An explicit user-requested version takes precedence over automatic classification. Record the override, synchronize that exact version, and do not silently substitute a different patch, minor, or major number.
Workflow
- Explain the chosen bump from the current root version.
- Update root and desktop package/lockfile versions.
- Update the OpenAPI version example and regenerate
openapi.yaml. - Update the deployment surface:
docker-compose.ymlimage tags (ccam-dashboard,ccam-mcp), the Helm chart'sversionandappVersion, everydeployments/kubernetes/**version label, image tag, and kustomizenewTag, anddeployments/scripts/deploy.sh(both the--tagexample and thesedsubstitution). - Update the release shown in
DEPLOYMENT.md,docs/DEPLOYMENT.md, andCITATION.cff. - Update version-sensitive UI snapshots; the dashboard renders
UI build v<version>, so regenerate and confirm the diff is only that line. - Run
npm run extensions:syncto regenerate Claude/Codex plugin manifests and both marketplaces. - Keep independently shipped client/MCP/monitoring/VS Code package versions unchanged unless explicitly included.
- Create or reuse the exact open GitHub milestone
v<version>for the new root version. Query all milestones first. If the exact title already exists closed or more than once, stop and resolve that release state instead of creating a duplicate. - Assign the current open pull request containing the bump to
v<version>. Read itsclosingIssuesReferencesand assign every linked closing issue to the same milestone. If no PR exists yet, leave this step explicitly incomplete until the PR is created. - Verify the PR and every linked issue report the expected milestone with fresh GitHub reads.
- Run
npm run extensions:validate, relevant tests/builds, and the CLI version check. - Never create or move a release tag without explicit user approval.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 91 lines · 50 tokens per session scan A 457ad12e2793
version-release is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 1,402 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-30.
Other skills, from other repositories
pull-request
Use this whenever the user asks to "open a PR", "ship this", "create the pull request", "make a PR", or once a feature/fix is verified and ready to push. Full lifecycle: branch → commit (commitizen) → issue → draft PR → CI → ready → autonomous monitor loop (fix comments, resolve threads, iterate until CI green + zero…
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
changelog
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.