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/entityprocess/agentv/deploy-pipelinegit clone --depth 1 https://github.com/EntityProcess/agentvWhat 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.00012 | $0.00106 |
| Opus 5 | $0.00006 | $0.00053 |
| Sonnet 5 | $0.00002 | $0.00021 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
deploy-pipeline 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 yesterday.
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
Deploy Pipeline
Input
$ARGUMENTS = path to release specification
Execution
Phase 1 — Plan
Load and follow: skills/deploy-plan/SKILL.md
Phase 2 — Execute
Load and follow: skills/deploy-execute/SKILL.md
Phase 3 — Verify
Run integration tests and produce a deployment report.
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.
- yesterday First seen · 25 lines · 12 tokens per session scan A ee46d3cc6a36
deploy-pipeline is a command published in the GitHub repository EntityProcess/agentv (15 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 106 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
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
README
Git workflow and quality assurance commands for the claude-skills repository.
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.