Borrowing it
Nothing to install: this file belongs to vishalguptax/claude-code-manager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vishalguptax/claude-code-manager/main/.claude/skills/release/SKILL.mdgit 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/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/vishalguptax/claude-code-manager/release"><img src="https://agentmods.dev/badge/skills/vishalguptax/claude-code-manager/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 196 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00056 | $0.01666 |
| Opus 5.5 | $0.00022 | $0.00666 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (32 stars, last pushed 2d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,666 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
github-ops
GitHub remote operations and README authoring: repo creation, metadata, releases, issue/PR management with preview-before-send, README as a landing page (badge row, features-as-benefits, screenshots, Recent Updates), and read-only security auditing. Triggers on: write a README, improve the README, README badges…
ci-cd-ops
CI/CD pipeline patterns with GitHub Actions, release automation, and testing strategies. Use for: github actions, workflow, CI, CD, pipeline, deploy, release, semantic release, changesets, goreleaser, matrix, cache, secrets, environment, artifact, reusable workflow, composite action.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, canonical sync, Core preview checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
ship
Commit, push, create PR(s), and auto-finalize — full automation pipeline. Handles uncommitted changes and recently created PRs.
promote-release
Prepare a release on develop and promote it to main on a git-flow repo. Confirm the auto-merging release-please PR landed on develop, validate the promotion, and merge develop to main with a merge commit; release-please tags on promotion. Refuses on trunk repos (default branch main) — use /merge-pr instead.