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/ilyasibrahim/claude-agents-coordinationWrote 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/ilyasibrahim/claude-agents-coordination/slo)<a href="https://agentmods.dev/commands/ilyasibrahim/claude-agents-coordination/slo"><img src="https://agentmods.dev/badge/commands/ilyasibrahim/claude-agents-coordination/slo.svg" alt="Measured on agentmods" 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.00012 | $0.00847 |
| Opus 5 | $0.00006 | $0.00424 |
| Sonnet 5 | $0.00002 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
slo 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 8d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLO Command
Invoke sre agent in reliability-review mode to define and analyze SLOs.
Usage
/slo [service-name] # Generate SLO document
/slo budget [service-name] # Calculate error budget status
/slo review [service-path] # Review existing SLO
Generate SLO Document
/slo [service-name]
Task(sre, "
Mode: reliability-review
Service: [service-name]
Generate comprehensive SLO document:
1. Service Overview
- Purpose and scope
- Key user journeys
- Critical dependencies
2. SLI Definitions
- Availability (success rate)
- Latency (P50, P95, P99)
- Error rate
- Throughput
3. SLO Targets
- Target percentages
- Measurement windows
- Rationale for each target
4. Error Budget
- Budget calculation
- Spend rate tracking
- Budget policy
5. Alerting Thresholds
- Warning vs critical
- Burn rate alerts
- Escalation paths
6. Failure Modes
- Known failure scenarios
- Impact assessment
- Mitigation strategies
7. Dependencies
- Upstream services
- Downstream consumers
- Dependency SLOs
Output: .claude/reports/sre/slo-[service]-YYYYMMDD.md
")
Error Budget Analysis
/slo budget [service-name]
Task(sre, "
Mode: reliability-review
Service: [service-name]
Analyze error budget status:
1. Current Period Status
- Budget allocated
- Budget consumed
- Burn rate
2. Trend Analysis
- Last 7 days
- Last 30 days
- Projected exhaustion
3. Budget Consumers
- Top incidents by budget impact
- Patterns in budget spend
4. Recommendations
- If healthy: feature velocity OK
- If degraded: reliability focus areas
- If exhausted: required actions
Output: .claude/reports/sre/budget-[service]-YYYYMMDD.md
")
SLO Reference
Standard SLO Tiers
| Tier | Availability | Monthly Downtime | Use Case |
|---|---|---|---|
| Tier 1 | 99.99% | 4.3 minutes | Payment, Auth |
| Tier 2 | 99.9% | 43.2 minutes | Core features |
| Tier 3 | 99.5% | 3.6 hours | Non-critical |
| Tier 4 | 99% | 7.2 hours | Internal tools |
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.
- 8d ago First seen · 145 lines · 12 tokens per session scan A 9c4cce549fac
slo is a command published in the GitHub repository ilyasibrahim/claude-agents-coordination (83 stars, last pushed 3mo ago), licensed Unlicense. It adds 12 tokens to every session and 847 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.