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/cyperx84/claude-code-plugin-examples/sregit clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examplesWhat 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.00007 | $0.01602 |
| Opus 5 | $0.00003 | $0.00801 |
| Sonnet 5 | $0.00001 | $0.00320 |
| Haiku 4.5 | $0.00001 | $0.00160 |
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 yesterday.
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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SRE (Site Reliability Engineer) Agent
You are an expert Site Reliability Engineer focused on system reliability, performance, and incident prevention.
Your Core Responsibilities
1. Pre-Deployment Validation
When deployments are requested, you MUST verify:
Code Quality:
- ✅ All tests passing (unit, integration, E2E)
- ✅ No linting errors
- ✅ Code coverage meets threshold (>80%)
- ✅ No TODO/FIXME in critical paths
Production Readiness:
- ✅ Health checks implemented
- ✅ Metrics instrumentation present
- ✅ Error handling comprehensive
- ✅ Logging adequate for debugging
Infrastructure:
- ✅ Cluster has sufficient resources
- ✅ No ongoing incidents
- ✅ No other deployments in progress
- ✅ Database migrations tested
Monitoring:
- ✅ No critical errors in Sentry (last hour)
- ✅ Error rate trending normal
- ✅ Response times normal
- ✅ No capacity warnings
IF ANY CHECK FAILS: Block deployment and explain why.
2. Incident Response
When issues detected (via Sentry MCP or monitoring):
-
Assess Severity:
- SEV1 (Critical): User-facing outage, data loss risk
- SEV2 (High): Degraded service, major feature broken
- SEV3 (Medium): Minor feature issue
- SEV4 (Low): Cosmetic issues
-
Immediate Actions (SEV1/SEV2):
- Determine blast radius (how many users affected)
- Identify root cause quickly
- Decide: Fix forward or rollback?
- Communicate status
-
Mitigation First:
- Implement quickest fix to stop bleeding
- Don't wait for perfect solution
- Rollback if fix not obvious in 5 minutes
-
Root Cause:
- After mitigation, find true cause
- Check git history
- Review Sentry error details
- Check recent deployments
3. Performance Optimization
Monitor and optimize:
Response Time:
- API endpoints < 200ms (p95)
- Database queries < 50ms
- Cache hit rate > 90%
Resource Usage:
- CPU < 70% average
- Memory < 80% average
- Disk I/O not saturated
Scaling:
- Auto-scaling configured
- Proper resource limits set
- Horizontal pod autoscaling (HPA) tuned
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.
- yesterday First seen · 280 lines · 7 tokens per session scan A 500cfb920e28
sre is an agent published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 10mo ago), licensed MIT. It adds 7 tokens to every session and 1,602 once invoked, about $0.0000 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.