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 elproximoframework/Skills_Ingenieria --skill slo-architectgit clone --depth 1 https://github.com/elproximoframework/Skills_IngenieriaWrote 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/elproximoframework/skills_ingenieria/slo-architect)<a href="https://agentmods.dev/skills/elproximoframework/skills_ingenieria/slo-architect"><img src="https://agentmods.dev/badge/skills/elproximoframework/skills_ingenieria/slo-architect/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/elproximoframework/skills_ingenieria/slo-architect"><img src="https://agentmods.dev/badge/skills/elproximoframework/skills_ingenieria/slo-architect.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.00164 | $0.02674 |
| Opus 5 | $0.00082 | $0.01337 |
| Sonnet 5 | $0.00033 | $0.00535 |
| Haiku 4.5 | $0.00016 | $0.00267 |
Grade A, and why
slo-architect 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 7d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
9 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.
- assets/error_budget_policy.md 2.6 KB
- assets/slo_template.yaml 2.2 KB
- references/composition.md 5.1 KB
- references/error_budget.md 4.5 KB
- references/sli_design.md 5.3 KB
- references/slo_principles.md 5.2 KB
- scripts/error_budget_calculator.py 5.5 KB runs code
- scripts/slo_designer.py 6.5 KB runs code
- scripts/slo_review.py 5.5 KB runs code
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.
- 7d ago First seen · 235 lines · 164 tokens per session scan A 63917f3e02ca
slo-architect is a skill published in the GitHub repository elproximoframework/Skills_Ingenieria (2 stars, last pushed 2mo ago), with no licence file. It adds 164 tokens to every session and 2,674 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
slo-architect
Use when defining, reviewing, or operating SLOs/SLIs/error budgets. Triggers on "define an SLO", "what should our SLO be", "error budget", "burn rate", "SLI", "service level objective", "Google SRE workbook", "multi-window burn-rate alert", or any reliability-target question. Ships SLO designer, error-budget…
slo-architect
Use when defining, reviewing, or operating SLOs/SLIs/error budgets. Triggers on "define an SLO", "what should our SLO be", "error budget", "burn rate", "SLI", "service level objective", "Google SRE workbook", "multi-window burn-rate alert", or any reliability-target question. Ships SLO designer, error-budget…
sre-expert
Expert-level site reliability engineering, SLOs, incident management, and operational excellence. Use when the user mentions reliability, monitoring, incident management, SLOs, or observability, or when the task involves SRE Fundamentals, Reliability Practices, SRE Principles, or On-Call.
reliability-engineering
SRE principles, observability, and incident management.
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
open_rca_diagnosis
A structured method for finding the root cause of failures in microservices by examining measurements, request traces, and logs. It uses thresholds and cross-checks to connect symptoms to causes.