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 agentmods add skills/tomzx/agents/create-service-levelsnpx skills add tomzx/agents --skill create-service-levelsgit clone --depth 1 https://github.com/tomzx/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/tomzx/agents/create-service-levels)<a href="https://agentmods.dev/skills/tomzx/agents/create-service-levels"><img src="https://agentmods.dev/badge/skills/tomzx/agents/create-service-levels.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.00030 | $0.01589 |
| Opus 5 | $0.00015 | $0.00794 |
| Sonnet 5 | $0.00006 | $0.00318 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade A, and why
create-service-levels 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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Service Levels
Defines the service-level objectives, indicators, agreements, and error budgets that govern a service's reliability.
Produces a single context-level artifact that observe-production checks against and audit-observability validates against.
Without explicit SLOs, reliability is judged by gut feel: no one knows when a degradation is acceptable, when to freeze feature work, or what "healthy" even means.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. .sdlc/context/architecture.md(must exist, to identify the services and their dependencies)..sdlc/context/goals.md(optional, to align reliability targets with project objectives)..sdlc/context/service-levels.md(optional; if present, revise rather than replace, per Revision Mode below).
Steps
- Read
.sdlc/context/architecture.mdto enumerate the services, endpoints, and critical user journeys. - Read
.sdlc/context/goals.mdif present, to align reliability targets with stated objectives. - For each critical user journey, define an SLI: what counts as a "good" event and a "total" event, and where that signal comes from.
- Set an SLO target per SLI (start conservative; tighten as you measure).
- Compute the error budget for each SLO (100% minus the target) and state the policy that applies when it is exhausted.
- Define SLAs only where a contractual or external obligation exists; keep SLA targets looser than SLOs so internal headroom protects the agreement.
- Specify burn-rate or threshold alerts that surface budget depletion before the window ends.
- Confirm the measurement infrastructure can actually produce each SLI signal; flag gaps as open questions.
- Write the machine-readable definitions (services, SLIs, SLOs with targets, windows, and error budgets, alert policies) to
.sdlc/context/service-levels.yamlin OpenSLO format (template atskills/sdlc/templates/context/service-levels.yaml). SLAs have no OpenSLO kind and stay in the markdown. Validate best-effort that the YAML parses and each SLO references an existing SLI and service. - Write the output to
.sdlc/context/service-levels.md. If it already exists, revise per Revision Mode.
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.
- 5d ago First seen · 102 lines · 30 tokens per session scan A 93b635f6634a
create-service-levels is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 1,589 once invoked, about $0.0002 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 skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…