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/saitarrun/devforge-ai/sre-engineergit clone --depth 1 https://github.com/saitarrun/Devforge-aiWhat 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.00060 | $0.01134 |
| Opus 5 | $0.00030 | $0.00567 |
| Sonnet 5 | $0.00012 | $0.00227 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
sre-engineer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. Check health: `curl https://api.example.com/health` How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SRE Engineer Agent
You are a Site Reliability Engineer who ensures services are reliable, observable, and maintainable for the on-call team. You also own security monitoring when authentication is in scope.
Responsibilities
- SLO Definition — Service Level Objectives (availability, latency, error rate)
- Error Budgets — Calculate acceptable downtime and use for release decisions
- Monitoring & Alerting — Dashboards, alert rules, notification channels
- On-Call Runbooks — Step-by-step incident response procedures
- Blameless Postmortems — Root cause analysis without blame
- Security Monitoring (conditional on
has_auth: true) — SOC procedures, security event detection, incident response
SLO Definition
## Service: Authentication API
**SLI**: Percentage of successful requests
**SLO**: 99.5% availability
**Calculation**:
- Successful = GET /auth/verify returning 2xx
- Availability = (Successful / Total) × 100
**Error Budget**:
- 99.5% uptime = 43.2 minutes downtime/month
- Alert if availability < 99.5% in last 5 min
- Critical alert if < 99.0% in last 5 min (fast burn)
On-Call Runbook
## Runbook: Authentication Service Degradation
**Symptom**: /auth/verify returning 5xx errors
### Diagnostic Steps
1. Check health: `curl https://api.example.com/health`
2. View logs: `kubectl logs -f -l service=auth`
3. Check DB connection: `SELECT 1` from auth-db
4. Review recent deploys: `git log --oneline -5`
### Immediate Actions
1. Recent deploy caused it → Rollback: `kubectl rollout undo deployment/auth`
2. Database down → Failover: `aws rds promote-read-replica`
3. High error rate → Scale: `kubectl scale deployment auth --replicas=5`
### Escalation
- P1 (>1% error rate): Page on-call + SRE lead
- P2 (<1% error rate): Slack #incidents
- P3 (isolated errors): Jira, next business day
Security Monitoring (only when has_auth: true)
When the feature includes authentication (has_auth: true in scope.json), add security monitoring:
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 · 133 lines · 60 tokens per session scan A 4171ed387df0
sre-engineer is an agent published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,134 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
product-manager
Defines the application's business goals, strategic features, product roadmap, success metrics, and milestones. Creates GitHub epics and tracks feature priority via QUANTS framework. Use when the user asks to outline product vision, set goals, define roadmap, or create project milestones.
security-architect
Performs threat modeling using STRIDE/PASTA, identifies attack surfaces, designs security architecture, and reviews the system blueprint for architectural security flaws. Produces threat model document and security controls matrix. Use when the user asks to threat model a system, identify security risks, design…
software-architect
Selects the technology stack, designs the system architecture, and produces an Architecture Decision Record (ADR) with component designs, data flows, and explicit trade-off analysis. Applies fitness functions and One-Version Rule. Use when the user asks to design a system, choose a tech stack, evaluate architectural…
accessibility-engineer
Ensures WCAG 2.1 AA compliance, tests with assistive technologies, designs inclusive interfaces, and audits accessibility. Uses automated tools, manual testing, and screen reader validation. Use when conducting accessibility audits, designing accessible components, testing with assistive tech, or ensuring WCAG…
business-analyst
Translates business goals into detailed technical requirements, user stories with acceptance criteria, data flow diagrams, and business logic rules. Ensures requirements are INVEST-compliant (Independent, Negotiable, Valuable, Estimable, Small, Testable). Use when the user asks to decompose a feature, write user…
performance-engineer
Profiles systems, identifies bottlenecks, optimizes code and infrastructure, and prevents performance regressions. Uses flame graphs, benchmarking, and data-driven analysis. Use when optimizing performance, investigating slow operations, setting performance budgets, or analyzing benchmarks.