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 skills/boshu2/agentops/sbhnpx skills add boshu2/agentops --skill sbhgit clone --depth 1 https://github.com/boshu2/agentopsWrote 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/skills/boshu2/agentops/sbh)<a href="https://agentmods.dev/skills/boshu2/agentops/sbh"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/sbh.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 | $0.00030 | $0.00640 |
| Opus 5 | $0.00015 | $0.00320 |
| Sonnet 5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
sbh 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SBH — storage pressure specialist
SBH exposes disk-pressure status, ballast, scanning, and recovery commands. This
skill gathers evidence and performs at most the explicit action authorized by the
caller. Its authorized actions can delete files and change host storage
configuration, so no mutation runs without explicit caller authority. The command
surface below is anchored to sbh 0.4.27; re-verify against sbh --version on
another host before relying on an exact flag.
Evidence-first recovery works because disk pressure has cheap reversible remedies and expensive irreversible ones; a factual baseline is what tells them apart before anything is deleted. Order remediation by irreversibility: status and dry runs first, ballast release next, cleanup of unprotected files after that, and emergency deletion last — never skip forward while a more reversible step remains untried.
Named failure mode — wrong-mount relief: reclaiming gigabytes on a filesystem that is not the constrained mount and declaring the pressure resolved.
Anti-pattern: escalating straight to emergency --yes because pressure is
critical. Corrective: urgency raises the stakes of an irreversible mistake; it
never lowers the authorization bar or the ordering above.
Constraints
- Begin with
sbh --json status,sbh check, or a dry run on the exact mount because recovery decisions need a factual baseline. - Never run
clean --yes,emergency --yes, ballast release,tune --apply,unprotect, or service/configuration changes without explicit authority because those operations mutate host state. - Preserve
.git/, open-file, young-file, non-writable-parent, and.sbh-protectvetoes because they prevent unsafe or ineffective cleanup. - Confirm that ballast or reclaimed bytes affect the constrained mount because free space on another filesystem does not resolve the pressure.
- Run one action once, capture before/after evidence, and stop because the caller owns any further mutation. A negative result is returned to the caller; this skill does not retry or escalate it.
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 · 67 lines · 30 tokens per session scan A fa7d7d8b14e5
sbh is a skill published in the GitHub repository boshu2/agentops (431 stars, last pushed 5d ago), licensed Apache-2.0. It adds 30 tokens to every session and 640 once invoked, about $0.0002 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 skills, from other repositories
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or…
doc-review
Use when the user asks to review or critique a prose planning document — a plan, spec, PRD, requirements doc, or design doc.
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
autolearn
Compound a solved problem into a durable in-repo learning doc. Use when a verified non-trivial fix lands, the user says "compound this", "document this fix", or "remember this". This is the automatic-capture entry point; for an explicitly requested one-off write-up, use compound.
doubt-driven
Doubt-driven adversarial review. Use when correctness matters more than speed, the code is unfamiliar, stakes are high, a claim can't be checked by the type system or compiler, or verifying now is cheaper than debugging later.
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.