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/undeadlist/claude-code-agents/release-prepnpx skills add undeadlist/claude-code-agents --skill release-prepgit clone --depth 1 https://github.com/undeadlist/claude-code-agentsWhat 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.00014 | $0.00359 |
| Opus 5 | $0.00007 | $0.00179 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
release-prep 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 2d 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
Release Prep Workflow
Prepare for a production release. Runs full audit, fixes critical issues, validates deployment readiness, and generates the release PR.
Execution (Sequential Phases)
Phase 1: Full Audit (Parallel)
Spawn all 11 audit agents in parallel (same as /full-audit):
- All auditors save reports to
.claude/audits/AUDIT_*.md
Phase 2: Fix Planning
Spawn fix-planner:
- Read all audit reports
- Create
.claude/audits/FIXES.mdwith prioritized action items
Phase 3: Critical Fixes
Spawn code-fixer:
- Implement P1 (critical) fixes only
- P2/P3 can wait for next release
Phase 4: Verification
Spawn test-runner:
- All tests pass (including after fixes)
- No regressions introduced
Phase 5: Deploy Validation
Spawn deploy-checker:
- Build succeeds
- Environment valid
- Dependencies clean
Phase 6: PR Generation
Spawn pr-writer:
- Generate release PR with summary of all changes
- Include audit findings and fixes applied
Release Criteria
Must Pass (Blockers)
- Zero P1 issues remaining
- All tests pass
- Build succeeds
- Deploy checker passes
Should Pass (Document if not)
- P2 issues addressed or documented
- Performance within acceptable range
- Documentation updated
Usage
/release-prep
Version: 2.1.0
Release date: 2024-03-15
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.
- 2d ago First seen · 63 lines · 14 tokens per session scan A cecb6bea575e
release-prep is a skill published in the GitHub repository undeadlist/claude-code-agents (147 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 359 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.