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 bregman-arie/devops-sre-skills --skill triage-latency-regressiongit clone --depth 1 https://github.com/bregman-arie/devops-sre-skillsWrote 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/bregman-arie/devops-sre-skills/triage-latency-regression)<a href="https://agentmods.dev/skills/bregman-arie/devops-sre-skills/triage-latency-regression"><img src="https://agentmods.dev/badge/skills/bregman-arie/devops-sre-skills/triage-latency-regression/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/bregman-arie/devops-sre-skills/triage-latency-regression"><img src="https://agentmods.dev/badge/skills/bregman-arie/devops-sre-skills/triage-latency-regression.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.00021 | $0.00418 |
| Opus 5 | $0.00010 | $0.00209 |
| Sonnet 5 | $0.00004 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
Triage Latency Regression 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 11d 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.
What it actually says
When to use
Use when p95/p99 latency increases and you need a fast root-cause hypothesis.
Preconditions
- You have access to metrics, logs, and (ideally) traces.
Procedure
- Confirm scope: which endpoints/operations, which regions, which customers.
- Compare before/after: deployment markers, config changes, dependency status.
- Decompose: queueing vs compute vs dependency latency.
- Validate saturation: CPU, memory, GC, thread pools, connection pools.
- Correlate errors/timeouts with latency.
Decision points
- Strong correlation with a deploy: consider rollback.
- Dependency latency increase: mitigate with timeouts, caching, failover.
- Saturation increase: scale, shed load, or reduce work.
Verification
- Latency returns to baseline and stays stable across multiple windows.
- Error rate does not regress.
Rollback / undo
- Roll back the most recent change correlated with the regression.
- Revert performance tuning if it degrades correctness.
Escalation
- Escalate to dependency owners if external system is the bottleneck.
- Escalate to service owners if code changes are required.
Examples
Example queries to adapt:
Compare p95 latency now vs 1h ago; split by route, status code, and upstream.
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.
- 11d ago First seen · 69 lines · 21 tokens per session scan A 9b7524e44afd
Triage Latency Regression is a skill published in the GitHub repository bregman-arie/devops-sre-skills (22 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 418 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 skills, from other repositories
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.
sre_triage
SRE first-response triage for distributed training incidents. Automates the manual checks from PyTorch/NCCL debugging runbooks.
pager-triage
AI-powered incident triage for PagerDuty. List active incidents, deep-dive with timeline and alert correlation, check on-call schedules, acknowledge, resolve, and annotate — all from your agent. Read-only by default; write operations require explicit --confirm.
Debugging Expert
Debugging Expert delivers production-grade technical work with clear architecture, tests, maintainability, and operational awareness.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
agent-qa-result-triage
Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.