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 commands/zevtos/agentpipe/releasegit clone --depth 1 https://github.com/zevtos/agentpipeWhat 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.00024 | $0.00628 |
| Opus 5 | $0.00012 | $0.00314 |
| Sonnet 5 | $0.00005 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are orchestrating a release. This combines changelog generation, version management, and deployment readiness into one workflow.
Context
@CLAUDE.md
Release Target
$ARGUMENTS
Auto-context
- Current version: !
git describe --tags --abbrev=0 2>/dev/null || echo "no tags yet" - Commits since last release: !
git log $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~50)..HEAD --oneline - Branch: !
git branch --show-current
Pipeline
Step 1: Determine Version
If the user specified a version, use it. If the user specified 'patch', 'minor', or 'major', calculate from current version. If nothing specified, analyze commits to determine:
- Any
feat:commits → minor bump - Only
fix:commits → patch bump - Any
BREAKING CHANGE:or!:→ major bump
Present: "Proposing version [X.Y.Z]. Correct?" Wait for confirmation.
Step 2: Changelog (Docs Agent)
Run the docs agent:
"Generate a release changelog for version [version].
Commits: [paste commit list from auto-context]
Format:
[version] - [today's date]
Added
[New features from feat: commits]
Changed
[Changes from refactor:/chore: commits that affect behavior]
Fixed
[Bug fixes from fix: commits]
Breaking Changes
[Breaking changes with migration instructions]
Security
[Security fixes if any]
Write each entry as one user-facing sentence in past tense. Include PR/issue numbers. Omit internal refactors that don't affect users."
Present the changelog. Ask: "Changelog look good? Any edits?"
Step 3: Pre-release Checks
Run the same checks as /deploy:
- All tests pass
- Build succeeds
- No critical dependency vulnerabilities
- No uncommitted changes
- On the correct branch (main/master)
Step 4: Create Release
After all checks pass:
- Update CHANGELOG.md (prepend new entry)
- Update version in package.json / pyproject.toml / Cargo.toml / version file
- Present the changes for review
Ask: "Ready to commit version bump and create tag [version]?"
On confirmation:
- Commit:
chore: release [version] - Create annotated tag:
git tag -a [version] -m "[version]: [one-line summary]" - Present: "Release [version] tagged. Push with
git push origin main --tagswhen ready."
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 · 82 lines · 24 tokens per session scan A 71cc22c0e74f
release is a command published in the GitHub repository zevtos/agentpipe (11 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 628 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.