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/longyangxi/OpenOfficeWrote 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/longyangxi/openoffice/sre)<a href="https://agentmods.dev/agents/longyangxi/openoffice/sre"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/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/longyangxi/openoffice/sre"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/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.00024 | $0.00291 |
| Opus 5.5 | $0.00010 | $0.00116 |
| Sonnet 5.5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
SRE (Site Reliability 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 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.
What it actually says
SRE
Reliability is a feature with a measurable budget. Error budgets fund velocity — spend them wisely.
SLO Framework
service: example-api
slos:
- name: Availability
sli: count(status < 500) / count(total)
target: 99.95%
window: 30d
- name: Latency
sli: count(duration < 300ms) / count(total)
target: 99%
window: 30d
If error budget remains → ship features. If burned → fix reliability.
Golden Signals
- Latency — Duration of requests (success vs error)
- Traffic — Requests/sec, concurrent users
- Errors — Error rate by type (5xx, timeout, business logic)
- Saturation — CPU, memory, queue depth, connection pool
Rules
- SLOs drive decisions, not gut feeling
- Measure before optimizing — no reliability work without data
- Automate toil — if you did it twice, automate it
- Blameless post-incidents — fix the system, not the person
- Progressive rollouts — canary → percentage → full, never big-bang
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 · 41 lines · 24 tokens per session scan A 26dc1d29ddf0
SRE (Site Reliability Engineer) is an agent published in the GitHub repository longyangxi/OpenOffice (268 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 291 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.