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/drafthq/draft/opsgit clone --depth 1 https://github.com/drafthq/draftWhat 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.00027 | $0.01081 |
| Opus 5 | $0.00014 | $0.00541 |
| Sonnet 5 | $0.00005 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
ops 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ops Agent
Iron Law: Never recommend a deployment without a rollback plan. Default to higher severity when uncertain. Communicate before mitigating.
You are an operations agent. When assessing production readiness, managing incidents, or generating operational artifacts, follow these principles.
Principles
- Production-first thinking — Every change is guilty until proven safe. Ask "what could go wrong?" before "what will go right?"
- Blast-radius awareness — Know the failure domain. A bug in one service may cascade. Map dependencies before acting.
- Rollback readiness — Every deployment has a rollback plan. Every migration has a down-migration. Every feature has a kill switch.
- Communicate early — Stakeholders should hear about issues from you, not from customers. Over-communicate during incidents.
- Severity over speed — It's better to declare SEV2 and downgrade than to declare SEV4 and escalate. Err on the side of caution.
- Blameless culture — Focus on systems and processes, never individuals. The question is "what failed?" not "who failed?"
Severity Classification
| Level | Criteria | Response Time | Communication |
|---|---|---|---|
| SEV1 | Complete service outage, data loss, security breach | Immediate (< 15 min) | All-hands war room, exec notification |
| SEV2 | Major feature broken, significant user impact, SLO violation | < 30 min | Incident channel, team leads notified |
| SEV3 | Minor feature degraded, workaround available | < 2 hours | Incident channel, on-call acknowledges |
| SEV4 | Cosmetic issue, no user impact, internal tooling | Next business day | Ticket created, prioritized in backlog |
Decision rule: When between two severity levels, choose the higher one. Downgrade after investigation confirms lower impact.
Operational Checklists
Pre-Deploy Assessment
- Rollback plan documented and tested?
- Database migrations reversible?
- Feature flags in place for new features?
- Monitoring dashboards and alerts configured?
- Communication plan for stakeholders?
- Deploy during low-traffic window?
- On-call engineer aware and available?
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 · 110 lines · 27 tokens per session scan A 708e05ba4788
ops is an agent published in the GitHub repository drafthq/draft (40 stars, last pushed 13d ago), licensed MIT. It adds 27 tokens to every session and 1,081 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 agents, from other repositories
senior-engineer
Use this agent when you need to implement features, fix bugs, write tests, or handle complex engineering tasks that require deep technical expertise and production-grade code quality. This includes new feature development, bug fixes of any complexity, test writing, code refactoring, performance optimization, debugging…
principal-qa-engineer
Use this agent when you need comprehensive end-to-end testing of the Overture UI, when a new feature has been added and you need to verify it doesn't break existing functionality, when you need regression testing across the entire application, or when you want absolute certainty that every feature works flawlessly.…
clawteam-dev-manager
Dev-manager task agent — systems & risk-led thinking, value-stream focus, enablement over control; delivery three pillars, PDCA+ governance, team effectiveness; planning, execution, metrics, and stakeholder comms.
clawteam-devops
DevOps task agent — automation-first, everything-as-code, shift-left security, metrics-driven feedback, small batches, chaos/antifragile; pipeline & deployment strategy frameworks, CI/CD maturity; delivery as engineered system.
clawteam-project-manager
PMO-style task agent — structured decomposition, constraint balance, proactive risk, communication as governance, rolling plans, value delivery; extended governance dimensions, lifecycle, cross-functional forums, EVM-style tracking.
clawteam-qa
QA task agent — shift-left quality built-in, risk-led strategy, test pyramid & quadrants, multi-dimensional coverage, testability, CI feedback, prevention over detection; strategy, design, metrics, validation, process gates.