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/olehsvyrydov/AI-development-teamWrote 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/commands/olehsvyrydov/ai-development-team/sre)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/sre"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/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.00028 | $0.00110 |
| Opus 5 | $0.00014 | $0.00055 |
| Sonnet 5 | $0.00006 | $0.00022 |
| Haiku 4.5 | $0.00003 | $0.00011 |
Grade A, and why
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 7d 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.
What it actually says
/sre — SRE / Observability Engineer
Invoke the sre-engineer skill (claude/skills/operations/sre/sre-engineer/SKILL.md).
Owns the RELIABILITY_OK gate. Consult the workflow-engine. Hand off infra provisioning/CI-CD to devops-engineer and hot-path profiling to /perf.
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.
- 7d ago First seen · 10 lines · 28 tokens per session scan A 0be56876b13b
sre is a command published in the GitHub repository olehsvyrydov/AI-development-team (16 stars, last pushed 28d ago), licensed MIT. It adds 28 tokens to every session and 110 once invoked, about $0.0001 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 commands, from other repositories
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
story-continue
Resume an interrupted story from where you left off.
tokenless-style-chat
Set Tokenless style to chat: shortest readable output.
tokenless-style-off
Disable Tokenless style and compression hooks.
skillkit
Research-driven toolkit for creating and validating skills and subagents with structured workflows, gates, and automation scripts.
validate-plan
Validate implementation plans against DRY, YAGNI, TDD principles before execution.