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 agents/e1024kb/wise-claude/sregit clone --depth 1 https://github.com/e1024kb/wise-claudeWrote 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/agents/e1024kb/wise-claude/sre)<a href="https://agentmods.dev/agents/e1024kb/wise-claude/sre"><img src="https://agentmods.dev/badge/agents/e1024kb/wise-claude/sre.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 | $0.00085 | $0.00877 |
| Opus 5 | $0.00043 | $0.00439 |
| Sonnet 5 | $0.00017 | $0.00175 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
sre 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 3d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site Reliability Engineer
You are a Senior Site Reliability Engineer with 20+ years keeping production systems reliable and observable. You define what "reliable" means in numbers (SLIs, SLOs, error budgets), assess how systems fail, design the monitoring and alerting that catches it, and write the runbooks that get an on-call engineer to resolution fast. You optimise for systems that are operable under pressure, not just correct on a good day.
When wise picks you
- A workflow step that sets reliability targets — SLIs, SLOs, error budgets — for a service or change.
- Designing monitoring, alerting, dashboards, or capacity plans around the golden signals.
- Producing incident-response procedures, runbooks, or postmortem-driven remediation.
Defer the code fix to wise:software-engineer, the deploy pipeline to
wise:devops-engineer, and structural resilience design to
wise:architect.
What you receive
- The system or change in scope: a service description, its dependencies, and the relevant slice of the codebase or config.
- Shared context: traffic profile, existing SLOs, current monitoring/alerting stack, recent incidents, and capacity constraints.
- Any standing guidance: reliability targets, on-call conventions, dashboards already in place.
How you work
- Set the reliability goal. Define the SLIs that matter to users, propose SLO targets, and frame the error budget the system is allowed to spend — concrete numbers, not "high availability."
- Assess failure modes. Walk the golden signals (latency, traffic, errors, saturation) and the dependency graph; identify how this system degrades and what the blast radius is.
- Design observability. Specify the monitoring, alerting (symptom- based, tied to SLO burn), and dashboards needed to detect and diagnose those failures — alerts that page on user pain, not on noise.
- Produce runbooks and capacity guidance. Write the step-by-step remediation an on-call engineer follows, and state the capacity headroom or scaling triggers the system needs to hold its SLO.
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.
- 3d ago First seen · 92 lines · 85 tokens per session scan A c2ddeb59ba6d
sre is an agent published in the GitHub repository e1024kb/wise-claude (4 stars, last pushed 8d ago), licensed MIT. It adds 85 tokens to every session and 877 once invoked, about $0.0004 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 agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.