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 rjmurillo/ai-agents --skill slo-designergit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/slo-designer)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/slo-designer"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/slo-designer/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/rjmurillo/ai-agents/slo-designer"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/slo-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.02737 |
| Opus 5.5 | $0.00022 | $0.01095 |
| Sonnet 5.5 | $0.00011 | $0.00547 |
| Haiku 4.5 | $0.00006 | $0.00274 |
Grade A, and why
slo-designer 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 22d 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLO Designer
When this skill activates, you guide users through designing production-ready Service Level Objectives. Your role is to help identify critical user journeys, define measurable SLIs, set appropriate targets, and calculate error budgets.
Triggers
Activate when the user:
Design SLOs for my serviceDefine reliability targetsCalculate error budgetDefine SLIs for this systemWhat should my availability target be?
When to Use
Use this skill when:
- Defining reliability targets for a new or existing service
- Calculating error budgets for capacity planning
- Establishing SLIs and alerting thresholds
- Stakeholders ask "what should our availability target be?"
Use chaos-experiment instead when:
- Testing whether the system meets its SLOs through failure injection
- Validating resilience mechanisms work as designed
Use threat-modeling instead when:
- Analyzing security threats, not reliability targets
Core Concepts
| Term | Definition | Example |
|---|---|---|
| SLI | Service Level Indicator. Metric measuring service quality. | p99 latency, availability % |
| SLO | Service Level Objective. Target value for an SLI. | p99 < 200ms, 99.9% availability |
| SLA | Service Level Agreement. Contract with consequences. | 99.95% uptime or credits issued |
| Error Budget | Allowed failures before SLO breach. | 0.1% = 43 min/month downtime |
| Burn Rate | Speed of error budget consumption. | 2x burn = budget exhausted in 15 days |
Common SLI Categories
Availability
Percentage of successful requests.
availability_sli = (successful_requests / total_requests) * 100
Good for: APIs, web services, databases.
Latency
Response time percentiles (p50, p95, p99).
latency_sli = percentile(response_times, 99)
Good for: User-facing endpoints, real-time systems.
Throughput
Requests per second (RPS) or transactions.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 22d ago Changed · +5 lines 10a3bb6c5754
- 1mo ago First seen · 360 lines · 56 tokens per session scan A 2025c0f10b19
slo-designer is a skill published in the GitHub repository rjmurillo/ai-agents (48 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 2,737 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
install-gemini-code-review-action
Installs, configures, or upgrades Dazbo's PR code review & issue triage GitHub Action (gemini-review-action) in a target repository. Use when the user wants to set up, configure, or update automated AI code reviews, issue triaging, or Gemini model workflows for their GitHub repository.
review-deep
Review change vs spec, plan, code quality heuristics, and repo rules; append remediation phase if needed.
review-remote
Review open PR/MR and publish findings.
apply-review-feedback
Classify and apply accepted PR/MR review feedback.
azure-devops-automation
CI/CD pipelines, infrastructure as code, and deployment automation for Azure workloads.
architecture-audit
Comprehensive project consistency review across code, documentation, diagrams, and configuration.