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/longyangxi/openoffice/sregit clone --depth 1 https://github.com/longyangxi/OpenOfficeWhat 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.00024 | $0.00291 |
| Opus 5 | $0.00012 | $0.00146 |
| Sonnet 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 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.
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.
- 3d 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 (249 stars, last pushed 28d ago), licensed MIT. It adds 24 tokens to every session and 291 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.