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.
git clone --depth 1 https://github.com/latestaiagents/agent-skillsWrote 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/commands/latestaiagents/agent-skills/on-call-handoff)<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/on-call-handoff"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/on-call-handoff/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/commands/latestaiagents/agent-skills/on-call-handoff"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/on-call-handoff.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.00016 | $0.00961 |
| Opus 5 | $0.00008 | $0.00481 |
| Sonnet 5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
on-call-handoff 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/on-call-handoff
Generate a comprehensive handoff report for on-call rotation transitions.
What I Need
Tell me:
- Your name (outgoing on-call)
- Incoming on-call engineer's name
- Any specific issues to highlight
Or just run /on-call-handoff and I'll gather from connected tools.
Generated Handoff Report
# On-Call Handoff Report
**From:** [Outgoing Engineer]
**To:** [Incoming Engineer]
**Rotation:** [Team Name]
**Handoff Time:** YYYY-MM-DD HH:MM UTC
---
## 🚨 Active Incidents
| ID | Severity | Status | Summary | Started |
|----|----------|--------|---------|---------|
| INC-123 | SEV2 | Investigating | API latency spike | 2h ago |
**INC-123 Context:**
- Root cause: Suspected database connection pool exhaustion
- Current state: Scaled up read replicas, monitoring
- Next steps: Review connection pooling config tomorrow
- Key contacts: @dba-team if it recurs
---
## ⚠️ Watch Items
### High Priority
1. **Deployment in progress** - v2.3.4 rolling out to prod-west
- Canary at 10%, promoting to 50% at 14:00 UTC
- Rollback command ready: `kubectl rollout undo deploy/api`
2. **Elevated error rate** - payments-service at 0.5% (normal: 0.1%)
- Started after morning deploy, monitoring
- No user complaints yet
### Medium Priority
3. **Planned maintenance** - RDS maintenance window tonight 02:00-04:00 UTC
- Expected: 30s failover, auto-reconnect should handle
- Runbook: `database/rds-maintenance-checklist`
---
## 📊 System Health Summary
| Service | Status | Notes |
|---------|--------|-------|
| api-gateway | 🟢 Healthy | |
| user-service | 🟢 Healthy | |
| payments | 🟡 Degraded | Elevated errors, monitoring |
| search | 🟢 Healthy | |
| notifications | 🟢 Healthy | |
**Key Metrics (Last 24h):**
- Error rate: 0.12% (SLO: <0.5%) ✓
- P99 latency: 245ms (SLO: <500ms) ✓
- Availability: 99.95% (SLO: 99.9%) ✓
---
## 📝 Shift Summary
### Incidents Handled
- INC-121 (SEV3) - Resolved - Cache invalidation issue
- INC-122 (SEV4) - Resolved - Flaky test in CI
### Changes Made
- Scaled worker pool 3→5 instances (can scale back Monday)
- Updated alerting threshold for memory usage (was too noisy)
### Deferred Work
- [ ] Investigate slow query on reports endpoint (non-urgent)
- [ ] Update runbook for certificate rotation
---
## 📞 Key Contacts
| Role | Name | Reach |
|------|------|-------|
| Secondary On-Call | @jane | Slack, PagerDuty |
| Engineering Manager | @bob | Slack (daytime only) |
| DBA On-Call | @dba-team | PagerDuty |
| Security | @security-team | PagerDuty (SEV1 only) |
---
## 🔗 Quick Links
- [Runbooks](https://wiki.company.com/runbooks)
- [Dashboards](https://datadog.com/dashboard/main)
- [Incident Slack](https://slack.com/channels/incidents)
- [PagerDuty Schedule](https://pagerduty.com/schedules)
- [Status Page Admin](https://statuspage.io/admin)
---
*Handoff generated at YYYY-MM-DD HH:MM UTC*
*Good luck! 🍀*
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 · 136 lines · 16 tokens per session scan A f6dbb6c6f456
on-call-handoff is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 961 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 commands, from other repositories
fdk-react-create
Create a new Platform 3.0 React Meta app (default UI stack). Uses fdk create react-starter-template or react-meta skeletons with DEW components, metaConfig in manifest.json, and React Router.
fdk-refactor
Reduce function complexity in a Freshworks app to meet cyclomatic complexity ≤ 7 per function. Extracts helper functions, simplifies conditionals, and preserves behavior while improving code quality.
fw-setup-uninstall
Uninstall FDK completely — keeps Node.js and nvm (/fw-setup uninstall).
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.