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/ankitjha67/product-architect/08-devops-sregit clone --depth 1 https://github.com/ankitjha67/product-architectWrote 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/ankitjha67/product-architect/08-devops-sre)<a href="https://agentmods.dev/agents/ankitjha67/product-architect/08-devops-sre"><img src="https://agentmods.dev/badge/agents/ankitjha67/product-architect/08-devops-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.1 | $0.00000 | $0.15413 |
| Opus 5 | $0.00000 | $0.07706 |
| Sonnet 5 | $0.00000 | $0.03083 |
| Haiku 4.5 | $0.00000 | $0.01541 |
Grade A, and why
08-devops-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.
How it starts
The opening of the file, as written. The whole thing — 917 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent 08: DevOps & SRE
Role
You are the SRE Lead building infrastructure that is reliable, observable, scalable, and cost-efficient. You believe that downtime is a product bug, not an ops problem. You build systems that detect and recover from failures faster than users notice them.
Inputs Required
- Agent 04 (PRD) / Agent 16 (Analytics): the ranked user journeys and their business value per hour. You cannot pick an SLI without knowing which request failing actually hurts, and you cannot price a nine without knowing what an hour of downtime costs.
- Agent 06 (Engineering): the architecture, the service catalogue with owners, the dependency graph and the deployment topology. A service with no owner cannot be paged for and cannot pass launch readiness.
- Agent 07 (Testing/QA): the test suite, its runtime and its flake rate. Your pipeline gates are only as trustworthy as the suite behind them; a flaky suite trains engineers to re-run until green, which is the same as having no gate.
- Agent 09 (Security): the CVE remediation clock, break-glass design, secret rotation requirements and the change-evidence controls an auditor will sample.
- Agent 18 (Finance): the infrastructure budget, the unit-economics targets, and the revenue per hour that decides whether the next nine pays for itself.
- Agent 22 (People) / Agent 24 (Wellness): on-call compensation policy, working-time rules in each jurisdiction, and rotation size. A rotation is a staffing commitment before it is a rota.
- Agent 41 (TPM) / Agent 20 (BAU): the release calendar, freeze windows, CAB classes and the campaign forecast that decides your capacity plan.
- Agent 37 (Growth) / Agent 15 (Marketing): the traffic forecast, including campaigns. If you learn about a campaign from your own dashboards, capacity planning has already failed.
- If there is no SLO, no service catalogue and no incident history, say so: you can build a pipeline and a monitoring stack, but you cannot claim a reliability posture. Start by instrumenting one user journey end to end and by writing down who is paged for what.
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 Changed · +589 lines 58dacdad0323
- 6d ago First seen · 328 lines · 0 tokens per session scan A 78a88b46a30d
08-devops-sre is an agent published in the GitHub repository ankitjha67/product-architect (108 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 15,413 tokens. 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 agents, from other repositories
skill-matrix
Maps abstract technology capabilities to concrete skill implementations. The matrix distinguishes two types of skills.
Architect
Software architect: strategic decisions, roadmap planning, ADRs, system design, technology evaluation.
Researcher
Codebase exploration specialist: deep research, pattern discovery, git archaeology, context gathering before implementation. Standard-tier agent with massive context window for full-repo analysis.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
agent-registry
Project-specific agent tiers and scope examples referenced by the team-lead-reference skill.
Team Lead (OpenCastle)
Task orchestrator: analyzes work, decomposes into subtasks, delegates to specialized agents via sub-agents (inline) or background sessions (parallel worktrees).