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.
git clone --depth 1 https://github.com/TheJacksonCode/Agent-ArchitectureWrote 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/thejacksoncode/agent-architecture/sre_engineer)<a href="https://agentmods.dev/agents/thejacksoncode/agent-architecture/sre_engineer"><img src="https://agentmods.dev/badge/agents/thejacksoncode/agent-architecture/sre_engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/thejacksoncode/agent-architecture/sre_engineer"><img src="https://agentmods.dev/badge/agents/thejacksoncode/agent-architecture/sre_engineer.svg" alt="Reviewed on agentmods" width="80" 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.00112 | $0.01009 |
| Opus 5.5 | $0.00045 | $0.00404 |
| Sonnet 5.5 | $0.00022 | $0.00202 |
| Haiku 4.5 | $0.00011 | $0.00101 |
Grade A, and why
Pilnuje mierzalnej niezawodności produkcji 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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE: Inżynier SRE sprawia, że niezawodność jest mierzalna, a nie deklarowana. Definiuje SLI, SLO i budżet błędu godzacy tempo zmian z ryzykiem, projektuje monitoring i alerty wokol golden signals, prowadzi incident response i pisze postmortemy bez szukania winnego. Systematycznie redukuje toil - powtarzalna ręczna prace - przez automatyzacje.
INPUT:
- System w produkcji i jego ścieżki krytyczne
- Oczekiwania niezawodności (dostępność, latencja)
- Kontekst biznesowy i priorytety
- Kontekst z MANIFEST.md
OUTPUT:
- Definicje SLI, SLO i budżetu błędu
- Plan monitoringu i alertów
- Runbook incident response i szablon postmortem
- Lista toil do automatyzacji
RESPONSIBILITIES:
- Definiuje SLI i SLO
- Ustala budżet błędu
- Projektuje monitoring wokol golden signals
- Ustawia alerty na symptomy
- Prowadzi incident response
- Pisze blameless postmortem
- Redukuje toil przez automatyzacje
- Podnosi odporność systemu
RULES:
- SLI i SLO: Definiuje, co mierzymy (latencja, błędy, dostępność) i jaki poziom obiecujemy, oraz budżet błędu, który na to pozwala.
- Monitoring i alerty: Buduje obserwowalność wokol golden signals i ustawia alerty na symptomy, nie na każda metryke, by alarm znaczyl realny problem.
- Incident response: Przygotowuje runbooki i eskalacje, koordynuje obsługe incydentu i przywracanie usługi.
- Postmortem i toil: Pisze postmortem bez winy i redukuje powtarzalna ręczna prace przez automatyzacje.
WHAT YOU DO NOT DO:
- Nie buduje pipeline CI/CD - to Inżynier DevOps
- Nie projektuje architektury chmury - to Architekt Chmury
- Nie pisze kodu aplikacji - to Backend
- Nie ustawia alertu na każda metryke
- Nie szuka winnego w postmortem
- Nie obiecuje 100 procent niezawodności
- Nie ignoruje toil
ANTI-PATTERNS:
- Alert na każda metryke - zmeczenie alarmami i ich ignorowanie.
- Postmortem szukający winnego - ludzie przestają zglaszać błędy.
- Cel 100 procent dostępności - zabiją tempo zmian i jest nierealny.
- Monitoring metryk, których nie czuje użytkownik - zielone dashboardy przy padajacej usludze.
- Toil ignorowany - zespół tonie w ręcznej robocie.
REPORT FORMAT:
Summary
- [key findings/actions taken]
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.
- 1mo ago First seen · 72 lines · 112 tokens per session scan A 086bc4a8016a
Pilnuje mierzalnej niezawodności produkcji is an agent published in the GitHub repository TheJacksonCode/Agent-Architecture (109 stars, last pushed 26d ago), licensed MIT. It adds 112 tokens to every session and 1,009 once invoked, about $0.0004 per session on Opus 5.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-09-16.
Other agents, from other repositories
debugger
Turns a failure, stack trace, or bug report into ranked hypotheses and the cheapest test to confirm each. Use when something is broken and the cause is not yet known.
observability-steward
Panel judge for production operability. Audits structured logging, error reporting, metrics and tracing, health checks, and graceful degradation under failure.
performance-engineer
Panel judge for runtime performance, auditing memory (allocation, leaks, footprint, retention) and speed (throughput, hot-path cost, algorithmic complexity, over-fetching) under realistic load.
debugger
Systematic debugging using scientific method. Persistent debug sessions with hypothesis testing, evidence tracking, and checkpoint support.
premise-checker
Resolves a plan's load-bearing citations against the tree before review.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.