agentmods.dev

review-service-levels

review-service-levels is a skill for Claude Code, Codex from tomzx/agents. It costs 31 tokens per session (1,190 once invoked), scanned A, original, MIT.

A review tool for service-level objectives (SLOs), indicators (SLIs), agreements (SLAs), and error budgets used to define service reliability.

In plain words
What is it for?
Auditing service-level documents and their structured YAML configuration against architecture and project goals.
Why use it?
It checks whether reliability targets can be measured, cover the important services and user journeys, and support sound operating decisions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 8repo +2 yesterday A scan 31 tokens original MIT

Good fit Auditing service-level documents and their structured YAML configuration against architecture and project goals.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tomzx/agents/review-service-levels
View source ↗ tomzx/agents
Install

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.

Any agent
npx skills add tomzx/agents --skill review-service-levels
Clone the repo
git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for review-service-levels

README.md
[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/review-service-levels/github.svg)](https://agentmods.dev/skills/tomzx/agents/review-service-levels)
Your own site
<a href="https://agentmods.dev/skills/tomzx/agents/review-service-levels"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-service-levels/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.

agentmods 80×15 button for review-service-levels

Your own site · 80×15
<a href="https://agentmods.dev/skills/tomzx/agents/review-service-levels"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-service-levels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,190 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.01190
Opus 5 $0.00015 $0.00595
Sonnet 5 $0.00006 $0.00238
Haiku 4.5 $0.00003 $0.00119

Measured 8d ago against content hash 7513eb6a8cc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

review-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 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.

skills/review-service-levels/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review Service Levels

Audits a service-level objective set for measurability, coverage, policy soundness, and alignment with the architecture and goals.

Prerequisites

  • Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
  • .sdlc/context/service-levels.md, or an SLO document provided in context or as a file path.
  • .sdlc/context/architecture.md (to verify service and journey coverage).
  • .sdlc/context/goals.md (optional, to verify strategic alignment).

Steps

  1. Read the SLO document from .sdlc/context/service-levels.md if present, otherwise from context or as a file path.
  2. Read .sdlc/context/service-levels.yaml if present, and check it structurally (best-effort): the YAML parses, every SLO references an existing SLI and service, and each SLO has a target, window, and error budget. A failure is a blocking finding under Measurability.
  3. Cross-reference against the architecture (services, journeys) and goals, and confirm service-levels.yaml and service-levels.md agree (the YAML is normative on drift).
  4. Identify issues in each category below.
  5. Report findings. Omit any category that has no findings.
  6. Write the findings to .sdlc/context/review-service-levels.md with frontmatter artifact: service-levels, verdict (approved if no blocking findings, changes-requested if the author must address findings, rejected for a fundamental flaw), and reviewed_at: <ISO date>, with the findings as the body, per skills/sdlc/references/shared.md. Record any unresolved open questions in the findings body.

Review Checklist

Measurability

  • Is every SLI expressed as an explicit good/total ratio with both numerator and denominator defined?
  • Is the signal source for each SLI specified (metric, log, query), and does it actually exist in the measurement infrastructure?
  • Is a single rolling window used consistently across all SLOs (in the document and in service-levels.yaml)?
  • Are targets concrete percentages or counts (not "high" or "good")?

Read the full file on GitHub · 113 lines

Changes

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.

  1. 8d ago First seen · 113 lines · 31 tokens per session scan A 7513eb6a8cc8

Subscribe to this mod's changes

review-service-levels is a skill published in the GitHub repository tomzx/agents (8 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 1,190 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-09-03.

Analytics and metricsCloudDevOps and cloud
Related

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…

google/skills · 83 tokens

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).

google/skills · 73 tokens

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…

google/skills · 181 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

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".

microsoft/skills · 78 tokens

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…

Jeffallan/claude-skills · 71 tokens