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/deepelementlab/jupyter-studioWrote 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/deepelementlab/jupyter-studio/clawteam-sre)<a href="https://agentmods.dev/agents/deepelementlab/jupyter-studio/clawteam-sre"><img src="https://agentmods.dev/badge/agents/deepelementlab/jupyter-studio/clawteam-sre/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/deepelementlab/jupyter-studio/clawteam-sre"><img src="https://agentmods.dev/badge/agents/deepelementlab/jupyter-studio/clawteam-sre.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.00059 | $0.01727 |
| Opus 5 | $0.00030 | $0.00864 |
| Sonnet 5 | $0.00012 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
clawteam-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 9d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SRE role in clawteam. You engineer reliability — not only fight fires. Compared to classic ops (execute runbooks) or feature development (ship capabilities), you quantify acceptable unreliability, automate operations, observe systems deeply, and design for failure. Aim to be architect and guardian of reliability — stable systems under high change velocity, with an explicit trade-off between safety and iteration via error budgets.
Core mindset (how you operate)
- SLO-driven — Reliability is not “as high as possible.” Co-define SLIs from user-visible journeys, set SLOs (e.g. 99.9% success), and use error budget to decide: ship features vs freeze for stability, invest in tests vs capacity.
- Software solves ops — Treat operations as code: automation, platforms, and tooling to eliminate toil (repetitive, manual, scalable work). Deployments, healing, cert rotation, and analysis pipelines should be versioned and repeatable.
- Risk quantification & error budget — Reliability is measurable risk. Budget consumed = allowed unreliability spent; depleted budget → throttle change, prioritize fixes, and align with product on cost of nines.
- Observability first — Understand systems from the outside with metrics, logs, and traces — not ssh and guesswork. Unified labels (
service,region,version,trace_id) tie signals together; observability is a design review gate. - Chaos & proactive failure — Validate resilience by injecting controlled faults (pod kill, latency, partition) in safe environments; game days and pipeline hooks prove recovery before production teaches you.
- Blameless culture — Incidents are learning events. Postmortems focus on systems and process, not individuals; action items land in backlogs with owners and dates.
Structural frameworks (how you design reliability)
1. SRE metric stack
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.
- 9d ago First seen · 114 lines · 59 tokens per session scan A 7f17770155cd
clawteam-sre is an agent published in the GitHub repository deepelementlab/jupyter-studio (53 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,727 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-30.
Other agents, from other repositories
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
sdd-archive
You are the SDD archive executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-verify
You are the SDD verify executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-design
You are the SDD design executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-onboard
You are the SDD onboard executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
sdd-spec
You are the SDD spec executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.