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/vishalguptax/claude-code-manager/releasenpx skills add vishalguptax/claude-code-manager --skill releasegit clone --depth 1 https://github.com/vishalguptax/claude-code-managerWrote 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/vishalguptax/claude-code-manager/release)<a href="https://agentmods.dev/skills/vishalguptax/claude-code-manager/release"><img src="https://agentmods.dev/badge/skills/vishalguptax/claude-code-manager/release.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.00056 | $0.01666 |
| Opus 5 | $0.00028 | $0.00833 |
| Sonnet 5 | $0.00011 | $0.00333 |
| Haiku 4.5 | $0.00006 | $0.00167 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
Use this skill when the user says "release", "cut a release", "ship it", or similar.
This skill curates a release for the Claude Manager VS Code extension. The CI/CD workflow (.github/workflows/release.yml) handles the actual version bump, build, packaging, and publish to the Marketplaces — this skill just prepares human-readable release notes and decides the bump level via the commit message.
Flow
1. Verify git state
git status
git branch --show-current
- Working tree must be clean (no uncommitted changes)
- If not on
main, ask the user whether to merge the current branch first - Check there's anything to release:
git log $(git describe --tags --abbrev=0)..HEAD --onelinemust be non-empty
If no commits since last tag, stop and tell the user there's nothing to release.
2. Gather commits since last release
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
if [ -z "$LAST_TAG" ]; then
git log --oneline
else
git log $LAST_TAG..HEAD --oneline
fi
Read the list. Ignore commits authored by github-actions[bot] (those are auto-bumps).
3. Categorize commits
Group commits by conventional-commit prefix:
| Prefix | Section title |
|---|---|
feat: / feature: |
Features |
fix: |
Bug Fixes |
perf: |
Performance |
refactor: |
Refactoring |
docs: |
Documentation |
style: |
UI/Styling |
test: |
Tests |
build: / chore: / ci: |
Build / CI |
| anything else | Other |
Skip commits that are purely version bumps (release: v1.2.3) or merge commits (Merge branch) unless they carry meaningful content.
4. Decide bump level
Inspect commit messages to determine patch / minor / major:
- Major: any commit message contains
[major]or starts withbreaking:orBREAKING CHANGE - Minor: any commit message contains
[minor]or starts withfeat:orfeature: - Patch: anything else (fixes, chores, docs, perf, refactor, style)
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 · 208 lines · 56 tokens per session scan A 5d73916529d2
release is a skill published in the GitHub repository vishalguptax/claude-code-manager (28 stars, last pushed 25d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,666 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
ship
Commit and push changes with a pre-launch gate (validate-code + safe-repo) by default. --fast skips the gate.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
push-release
Push to GitHub and optionally bump version to trigger PyPI release.
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
changelog
AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…