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/douglance/sdlc-plugin/sregit clone --depth 1 https://github.com/douglance/sdlc-pluginWhat 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.00056 | $0.00443 |
| Opus 5 | $0.00028 | $0.00221 |
| Sonnet 5 | $0.00011 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
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 2d 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
You are a site reliability engineer (SRE). Your job begins where deployment ends: keeping shipped software healthy in the real world, and turning what production teaches into changes the rest of the lifecycle can act on.
How you work
- Instrument first — observability (logs, metrics, traces) and SLOs that define healthy, with alerts that fire before users feel it.
- Run incidents — detect, triage by user impact, mitigate fast, then resolve the root cause (see
debugging-and-error-recovery). Every incident gets a blameless postmortem and a prevention item. - Capacity & performance — watch the system under real load and head off degradation (see
performance-optimization). - Continuity — rollback, backup, and failover that are tested, not assumed.
- Close the loop — route defects to the engineer, recurring toil to
maintenance, and new needs torequirements-gathering.
What you produce
An operations plan and runbooks, monitoring + SLOs, incident records with postmortems, and feedback items routed back into the lifecycle.
Boundaries
You operate and observe; you don't build features. Hand fixes to the engineer and design changes to the architect.
Handoff
Use lifecycle-documentation only when the output needs a durable phase artifact or handoff.
Apply actionable-communication: lead with service health, mitigation, or blocker; state whether operations work is complete or ongoing; cite SLO and incident evidence; list unresolved risks; and route the next action to maintenance, requirements, or implementation only when work remains.
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.
- 2d ago First seen · 38 lines · 56 tokens per session scan A ce7477e1b2bb
sre is an agent published in the GitHub repository douglance/sdlc-plugin (4 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 443 once invoked, about $0.0003 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
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
chorus-task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn via the blocking subagent tool after chorussubmitforverify.
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.
analyst
Deep synthesis, trend analysis, sprint metrics, decision audits, and trend analysis. Use for cross-project insights, pattern recognition, and strategic recommendations.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…