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/curie-eng/curieWrote 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/plugins/curie-eng/curie/sre-bot)<a href="https://agentmods.dev/plugins/curie-eng/curie/sre-bot"><img src="https://agentmods.dev/badge/plugins/curie-eng/curie/sre-bot/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/plugins/curie-eng/curie/sre-bot"><img src="https://agentmods.dev/badge/plugins/curie-eng/curie/sre-bot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sre-bot 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 3d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "sre-bot",
"version": "0.1.2",
"description": "SRE triage assistant for plain-English production health and Kubernetes questions in Slack. One pinned upstream Kubernetes MCP connector exposes the core toolset: reads execute immediately, six mutations require a fresh human approval, and unmatched tools fail closed. Kubernetes RBAC limits writes to disposable demo-namespace workloads and independently excludes credentials, identity, RBAC, cluster-scoped mutation, and platform upgrades.",
"license": "Apache-2.0",
"author": {
"name": "CurieTech"
},
"keywords": [
"sre",
"observability",
"grafana",
"loki",
"prometheus",
"pyroscope",
"kubernetes",
"k8s",
"cluster",
"triage",
"approval-gated"
],
"starterPrompts": [
"Is anything broken right now?",
"Is any pod crashlooping or restarting?",
"Are all the nodes healthy?",
"Did anything get OOMKilled today?",
"Are there any alerts firing?",
"Which services are logging the most errors today?",
"Is the API slow right now?",
"Show me slow traces from the last hour"
],
"approvalPolicy": {
"gates": [
{
"gate": "mcp__curie__publish_changes",
"route": "sre-approvals"
},
{
"gate": "mcp__self-upgrade__upgrade_self",
"route": "sre-approvals"
},
{
"gate": "mcp__self-upgrade__upgrade_platform",
"route": "sre-approvals"
},
{
"gate": "mcp__kubernetes__pods_delete",
"route": "sre-approvals"
},
{
"gate": "mcp__kubernetes__pods_exec",
"route": "sre-approvals"
},
{
"gate": "mcp__kubernetes__pods_run",
"route": "sre-approvals"
},
{
"gate": "mcp__kubernetes__resources_create_or_update",
"route": "sre-approvals"
},
{
"gate": "mcp__kubernetes__resources_delete",
"route": "sre-approvals"
},
{
"gate": "mcWhat it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 198 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago Changed eb956f138d2a
- 9d ago Changed · +1 lines c22610e0c8f0
- 1mo ago Changed · +28 lines d916176f1558
- 1mo ago Changed · +78 lines c338703c16fa
- 1mo ago First seen · 49 lines scan A 6a41be3b62bd
sre-bot is a plugin published in the GitHub repository curie-eng/curie (37 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
ac
Plans before it edits, routes each step to haiku, sonnet or opus by cost, verifies four ways per wave, and can finish a run unattended behind a read-only gate. Ships tiered subagents, a QA pass, authoring skills, local MCP tools, and gated fail-open hooks.
ci-incident-medic
Triages failing GitHub Actions runs, hardens Dockerfiles, pre-flights Kubernetes manifests before they reach the cluster, and drafts blameless postmortems from incident evidence.
karellen-lsp-mcp
LSP-backed code intelligence for Claude Code via MCP and native LSP - navigate definitions, references, call hierarchies, type hierarchies, and diagnostics across codebases.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.
compact-nudge
Suggests /compact or /clear when the context grows past a threshold or the prompt cache has gone cold, since every request re-reads the whole context.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.