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 addxai/enterprise-harness-engineering --skill sre-agentgit clone --depth 1 https://github.com/addxai/enterprise-harness-engineeringWrote 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/addxai/enterprise-harness-engineering/sre-agent)<a href="https://agentmods.dev/skills/addxai/enterprise-harness-engineering/sre-agent"><img src="https://agentmods.dev/badge/skills/addxai/enterprise-harness-engineering/sre-agent/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/addxai/enterprise-harness-engineering/sre-agent"><img src="https://agentmods.dev/badge/skills/addxai/enterprise-harness-engineering/sre-agent.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.00116 | $0.01975 |
| Opus 5 | $0.00058 | $0.00988 |
| Sonnet 5 | $0.00023 | $0.00395 |
| Haiku 4.5 | $0.00012 | $0.00198 |
Grade A, and why
sre-agent 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 9d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sre-agent
Description
SRE Agent. Four operating modes, which can invoke each other.
Setup
Before using sre-agent, configure the following:
| Variable | Description | Required For |
|---|---|---|
PAGERDUTY_API_TOKEN |
PagerDuty API v2 Access Key | oncall / diagnosis / patrol |
NOTIFICATION_WEBHOOK_URL |
Notification webhook URL (e.g. Slack, Feishu, Teams) | oncall / patrol notifications |
NOTIFICATION_WEBHOOK_SECRET |
Webhook signing secret (if applicable) | oncall / patrol notifications |
Additionally, populate references/infra-context.md with your infrastructure details:
- Prometheus/Thanos/VictoriaMetrics endpoints
- Cloud account IDs and VPC CIDRs
- Kubernetes cluster contexts
- Available diagnostic skills
Mode Routing
Route to the appropriate mode based on $ARGUMENTS or user input characteristics:
| Input Characteristics | Mode | Rules File |
|---|---|---|
| "oncall", "check alerts", scheduled trigger | oncall | references/mode-oncall.md |
| Contains specific incidents / alert / alert content | diagnosis | references/mode-diagnosis.md |
| "patrol", "health check", "inspection" | patrol | references/mode-patrol.md |
| "iterate", "retrospective", "improve sre-agent" | iteration | references/mode-iteration.md |
| "check alerts", "ack", "resolve", PagerDuty operations | Use PagerDuty capability directly | references/capability-pagerduty.md |
After entering the corresponding mode, the rules file for that mode must be read and strictly followed.
Inter-Mode Call Relations
oncall ──invokes──> diagnosis (Triage dispatches Diagnosis Agent for deep investigation)
patrol ──invokes──> diagnosis (deep analysis of critical-level patrol findings)
diagnosis ─references─> patrol-playbook (consults known failure patterns to assist investigation)
oncall ──persists──> known-issues (written after user confirmation)
diagnosis ─reads─> known-issues (references known issues)
iteration ─reads/writes─> all references (improves sre-agent itself based on feedback)
What ships with it
21 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.
- references/capability-feishu.md 6.0 KB
- references/capability-pagerduty.md 5.0 KB
- references/capability-scripts-cleanup.md 1.5 KB
- references/infra-context.md 5.0 KB
- references/known-issue-evidence-standard.md 2.9 KB
- references/known-issues.md 4.5 KB
- references/mode-diagnosis.md 1.9 KB
- references/mode-iteration.md 7.3 KB
- references/mode-oncall.md 9.8 KB
- references/mode-patrol.md 6.3 KB
- references/patrol-playbook.md 5.7 KB
- references/report-standard.md 6.3 KB
- references/role-diagnosis.md 5.5 KB
- references/role-entry.md 4.8 KB
- references/role-patrol-l1.md 2.1 KB
- references/role-patrol-l2.md 1.0 KB
- references/role-triage.md 4.7 KB
- references/setup.md 2.9 KB
- scripts/feishu_notify.py 10.0 KB runs code
- scripts/pagerduty_api.py 12 KB runs code
- scripts/scripts-cleanup.sh 1.9 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.
- 9d ago First seen · 165 lines · 116 tokens per session scan A ca0e0ce1807f
sre-agent is a skill published in the GitHub repository addxai/enterprise-harness-engineering (44 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 116 tokens to every session and 1,975 once invoked, about $0.0006 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
bug-diagnosis
Use this skill to systematically diagnose the root cause of a bug before attempting a fix. Activates when a bug is reported, a test is failing, or unexpected behavior is observed. Prevents guess-and-check debugging that introduces additional bugs while chasing symptoms.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
peon-ping-toggle
Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session. Also handles config changes like volume, pack rotation, categories — any peon-ping setting.
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…