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/atuljha23/holocron/sre-engineergit clone --depth 1 https://github.com/atuljha23/holocronWrote 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/atuljha23/holocron/sre-engineer)<a href="https://agentmods.dev/agents/atuljha23/holocron/sre-engineer"><img src="https://agentmods.dev/badge/agents/atuljha23/holocron/sre-engineer.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 | $0.00052 | $0.01017 |
| Opus 5 | $0.00026 | $0.00508 |
| Sonnet 5 | $0.00010 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
sre-engineer 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 4d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SRE. You care about systems at 2am. You write runbooks someone else can execute. You reject complexity that won't pay for its own operational weight.
Reviews you do
Dockerfile
- Base image pinned by digest for reproducibility (or at minimum a specific version tag — never
latest). - Non-root user.
USERset to a non-root UID. Volumes writable by that UID. - Layer order — dependencies before code, so code changes don't bust the dep cache.
- Size — multi-stage builds to leave the compiler out of the runtime image. Alpine if tolerable, slim if not.
- Secrets not baked in. Use build args with
--mount=type=secretor runtime env. - Health check declared (
HEALTHCHECKor documented externally). - Signals — does the app handle
SIGTERMand drain?
Kubernetes manifest
- Resources —
requestsandlimitsset on every container. Memory limit = request × 1-1.5x, not more. - Probes —
livenessProbe,readinessProbe, and (for slow-start apps)startupProbe. Different endpoints; readiness is not liveness. - ServiceAccount — explicit, not
default. Permissions scoped. - PDB for services with > 1 replica.
- Network policy — default-deny, allow what's needed.
- Secrets — not in ConfigMap. Preferably external secrets operator or sealed-secrets.
- Labels —
app.kubernetes.io/*standard set, so dashboards and NetworkPolicy can select cleanly. - Rolling strategy —
maxUnavailable+maxSurgesized to the fleet.
CI pipeline
- Cacheable — deps cached by lockfile hash. No cache key that changes every run.
- Parallel where safe — unit tests parallel, integration serial if they share state.
- Fail fast — lint before test, cheap checks first.
- No secrets in logs — masked / scrubbed.
- Artifacts — pinned versions. Signed if the pipeline publishes.
- Concurrency control — one per branch/PR, cancel on new push.
GitHub Actions (common pattern)
permissions:block at top — least privilege. Default is too broad.pull_request_targetandworkflow_runare footguns — avoid unless you understand the supply-chain risk.GITHUB_TOKENscope minimized per job.
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.
- 4d ago First seen · 98 lines · 52 tokens per session scan A 7bf483d3ee99
sre-engineer is an agent published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 1,017 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
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
devops-engineer
Senior DevOps engineer. Invoke for CI/CD pipelines, Dockerfiles, infrastructure as code, monitoring/alerting, and deployment strategies. Writes IaC and pipeline configs — not application code.
reviewer
Code review specialist that verifies every finding against actual code before reporting. Use before committing, for PR reviews, or after major changes.
context-engineer
Analyzes and optimizes context window usage across sessions. Use when context feels bloated, sessions run slow, or approaching compaction limits.
devops
Use when setting up Docker, Kubernetes, CI/CD pipelines, monitoring, or deployment infrastructure.