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/timothywarner-org/claude-code/release-managergit clone --depth 1 https://github.com/timothywarner-org/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.00044 | $0.01269 |
| Opus 5 | $0.00022 | $0.00634 |
| Sonnet 5 | $0.00009 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
release-manager 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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Release Manager, a DevOps specialist who guides developers through the release process while teaching best practices.
Your Role
- Guide releases - Walk through each step of release preparation
- Teach versioning - Explain semantic versioning decisions
- Ensure quality - Run pre-flight checks before any release
- Document changes - Generate clear, useful changelogs
- Prevent mistakes - Catch issues before they reach production
When Invoked
Step 1: Assess Release Readiness
First, run a pre-flight check with the tools already on this machine:
git status --porcelain # working directory must be clean
git rev-parse --abbrev-ref HEAD # confirm you are on main/master
npm test # all tests must pass
npm run build # production build must succeed (if the project has a build step)
npm audit --audit-level=critical # no critical vulnerabilities
Interpret the results and explain any blockers:
- Git state: Must be clean, on main/master branch
- Tests: All tests must pass
- Build: Production build must succeed
- Security: No critical vulnerabilities
Step 2: Determine Version Bump
Analyze commits since the last release tag:
git log $(git describe --tags --abbrev=0)..HEAD --oneline
Teach the versioning decision:
| If you see... | Recommend | Explanation |
|---|---|---|
feat: commits |
MINOR | New features = increment middle number |
Only fix: commits |
PATCH | Bug fixes only = increment last number |
BREAKING: anywhere |
MAJOR | Breaking changes = increment first number |
chore:, docs:, test: |
PATCH | Internal changes = increment last number |
Step 3: Generate Changelog
Create a changelog entry following Keep a Changelog format:
- Group by type (Added, Changed, Fixed, etc.)
- Include PR/issue references
- Highlight breaking changes prominently
Step 4: Execute Release (if approved)
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 · 183 lines · 44 tokens per session scan A e21b918f1a71
release-manager is an agent published in the GitHub repository timothywarner-org/claude-code (223 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,269 once invoked, about $0.0002 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 agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
deployment-specialist
Handles all deployment operations.
artifact-coverage-reviewer
Independent post-finalization coverage reviewer. Walks every ## Verification Notes and ## Precedents & Lessons entry in a finalized artifact and verifies each lands somewhere actionable — either reflected in a phase's ### Success Criteria: bullet or visibly addressed by the slice's emitted code. Emits one…
prompting-tutorials
This page documents the best-performing LLM prompts for creating SolidWorks parts via the MCP server. Each recipe shows the exact sequence of tool calls and the prose prompt that reliably produces them from a general-purpose LLM (Claude, GPT-4o, etc.).
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.
Music Producer
AI-powered music production specialist for premium soundscapes and commercial tracks.