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/slo-report)<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/slo-report"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/slo-report/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/slo-report"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/slo-report.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.00013 | $0.00993 |
| Opus 5 | $0.00006 | $0.00496 |
| Sonnet 5 | $0.00003 | $0.00199 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade A, and why
slo-report 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 9d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/slo-report
Generate SLO status reports with error budget consumption, trends, and recommendations.
What I Need
Tell me:
- Time period (last week/month/quarter)
- Specific service or all services
- Report format (summary/detailed)
Sample Report
# SLO Status Report
**Period:** January 2026
**Team:** Platform Engineering
**Generated:** 2026-02-01
---
## Executive Summary
| Status | Services |
|--------|----------|
| 🟢 Healthy | 8 |
| 🟡 At Risk | 2 |
| 🔴 Breached | 0 |
**Overall Error Budget:** 67% remaining (was 78% last month)
---
## Service-by-Service Status
### api-gateway
| SLO | Target | Actual | Status | Budget |
|-----|--------|--------|--------|--------|
| Availability | 99.9% | 99.95% | 🟢 | 85% |
| Latency P99 | <200ms | 156ms | 🟢 | 100% |
| Error Rate | <0.1% | 0.04% | 🟢 | 92% |
**Trend:** ↗️ Improving (+5% budget vs last month)
---
### payments-service
| SLO | Target | Actual | Status | Budget |
|-----|--------|--------|--------|--------|
| Availability | 99.99% | 99.97% | 🟡 | 23% |
| Latency P99 | <500ms | 467ms | 🟢 | 78% |
| Error Rate | <0.05% | 0.03% | 🟢 | 85% |
**Trend:** ↘️ Declining (-15% budget vs last month)
**⚠️ At Risk:** Availability budget consumed faster than expected
- 3 incidents this month (INC-121, INC-125, INC-128)
- Projected budget exhaustion: Feb 15
**Recommendations:**
1. Prioritize reliability work over new features
2. Review INC-128 postmortem action items
3. Consider adding redundancy to payment processor
---
### search-service
| SLO | Target | Actual | Status | Budget |
|-----|--------|--------|--------|--------|
| Availability | 99.5% | 99.82% | 🟢 | 100% |
| Latency P99 | <1000ms | 678ms | 🟢 | 100% |
| Relevance | >85% | 87% | 🟢 | 100% |
**Trend:** → Stable
---
## Error Budget Consumption
January Error Budget Burn Rate
api-gateway ████░░░░░░░░░░░░░░░░ 15% consumed payments ████████████████░░░░ 77% consumed ⚠️ user-service ██████░░░░░░░░░░░░░░ 28% consumed search ░░░░░░░░░░░░░░░░░░░░ 0% consumed notifications ████████░░░░░░░░░░░░ 35% consumed
## Incidents Impact
| Incident | Duration | Services | Budget Impact |
|----------|----------|----------|---------------|
| INC-121 | 23 min | payments | -12% |
| INC-125 | 8 min | payments, api | -5% |
| INC-128 | 45 min | payments | -18% |
| INC-130 | 5 min | notifications | -3% |
## Recommendations
### Immediate (This Week)
1. 🔴 **payments-service**: Implement circuit breaker for payment processor
2. 🟡 **api-gateway**: Review rate limiting configuration
### This Month
3. Add synthetic monitoring for critical paths
4. Implement SLO alerting at 50% budget consumption
5. Schedule quarterly SLO review meeting
### This Quarter
6. Evaluate SLO targets - some may be too aggressive
7. Implement error budget-based deployment gates
---
*Report generated from Datadog SLO data*
*Next review: 2026-02-01*
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.
- 9d ago First seen · 133 lines · 13 tokens per session scan A 5c347fb44e99
slo-report is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 993 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.
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.