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 skills add camilooscargbaptista/cto-toolkit --skill on-call-designgit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/on-call-design)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/on-call-design"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/on-call-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/on-call-design"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/on-call-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00018 | $0.01118 |
| Opus 5 | $0.00009 | $0.00559 |
| Sonnet 5 | $0.00004 | $0.00224 |
| Haiku 4.5 | $0.00002 | $0.00112 |
Grade A, and why
on-call-design 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 10d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
On-Call Design & Incident Response
When to Use
- Setting up on-call rotation for the first time
- Improving existing on-call process (too many pages, burnout)
- Designing escalation tiers
- Standardizing runbooks across teams
Rotation Design
Tier Model
Tier 1 (First Responder):
Who: Engineer on rotation (weekly cycle)
SLA: Acknowledge in 5 min, respond in 15 min
Scope: All production alerts for their service(s)
Tier 2 (Specialist):
Who: Senior engineer / tech lead
SLA: Respond in 30 min
Scope: Escalated issues, cross-service problems
Tier 3 (Leadership):
Who: Engineering manager / CTO
SLA: Respond in 1 hour
Scope: Major incidents, customer-facing outages, data breaches
Schedule Patterns
| Pattern | Team Size | Pros | Cons |
|---|---|---|---|
| Weekly rotation | 4+ engineers | Simple, predictable | Long shifts |
| Follow-the-sun | 8+ (multi-TZ) | No night pages | Coordination overhead |
| Primary/Secondary | 6+ | Backup coverage | Requires 2 people always |
| Business hours only | 3+ | No night pages | Gaps in coverage |
| Hybrid | 5+ | Balanced | Complex scheduling |
Recommended: Weekly Primary/Secondary
Week 1: Alice (primary), Bob (secondary)
Week 2: Bob (primary), Carol (secondary)
Week 3: Carol (primary), Dave (secondary)
Week 4: Dave (primary), Alice (secondary)
Rules:
- Primary: first responder, expected to resolve or escalate
- Secondary: backup if primary doesn't acknowledge in 10 min
- Handoff: Monday 10am (overlap with both people)
- Minimum 4 weeks between primary shifts
- Never on-call during PTO
Escalation Policy
# PagerDuty/OpsGenie-style escalation
escalation_policy:
name: "Backend API"
repeat_count: 2 # Retry full chain 2x before giving up
steps:
- timeout_minutes: 5
targets:
- type: on_call_primary
- timeout_minutes: 10
targets:
- type: on_call_secondary
- timeout_minutes: 15
targets:
- type: team_lead
- notification: slack_channel_critical
- timeout_minutes: 30
targets:
- type: engineering_manager
- notification: phone_call
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.
- 10d ago First seen · 142 lines · 18 tokens per session scan A 7d77d02705ec
on-call-design is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 1,118 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-31.
Other skills, from other repositories
Incident Response Planner
Analyze an infrastructure incident alert and produce a structured response plan plus an executable on-call runbook. Use for incident, alert, on-call, and runbook requests.
write-ops-runbook
Use when documenting a repeatable operational procedure that on-call engineers or operators must execute under pressure.
Alerting & Monitoring Testing
Testing monitoring and alerting configurations including threshold validation, alert routing, escalation policies, and false-positive rate monitoring.
runbook-authoring
Author operational runbooks so every alert maps to a tested, copy-pasteable, idempotent recovery procedure with diagnosis, remediation, escalation, rollback, and verification.
runbook-authoring
Write runbooks that a sleepy oncall engineer at 3am can actually follow. Invoke when shipping anything pageable, or when a runbook is stale after a postmortem.
sre-runbooks
Safe-by-default DevOps/SRE runbook automation for incident response, postmortems, on-call handovers, and operational troubleshooting. Implements Google SRE principles with agent-safe execution patterns including dry-run modes, human approval gates, and blast-radius limits.