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/shwetank/bettersense/engineering-reliabilitygit clone --depth 1 https://github.com/shwetank/bettersenseWrote 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/shwetank/bettersense/engineering-reliability)<a href="https://agentmods.dev/agents/shwetank/bettersense/engineering-reliability"><img src="https://agentmods.dev/badge/agents/shwetank/bettersense/engineering-reliability.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.00017 | $0.01615 |
| Opus 5 | $0.00009 | $0.00807 |
| Sonnet 5 | $0.00003 | $0.00323 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
engineering-reliability 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 2d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 2d ago First seen · 100 lines · 17 tokens per session scan A 313786856164
engineering-reliability is an agent published in the GitHub repository shwetank/bettersense (3 stars, last pushed 1mo ago), with no licence file. It adds 17 tokens to every session and 1,615 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-09-03.
Other agents, from other repositories
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
customer-experience
Customer Experience (CCO). Owns plugins/customer-experience/ and nothing else. Delegate work in this department's remit here.
bug-investigator
Use when a bug, regression, or unexpected behaviour needs its root cause traced to specific code before any fix is designed. Investigates only — never edits files. Returns a structured report citing file:line evidence.
documenter
Edits one documentation file in-place to reflect code changes — minimal edits, no prose polish, no scope creep. Operates in UPDATE mode (file exists) or CREATE mode (file is new). Dispatched by /hyperclaude:hyper-docs-sync once per affected doc. Context: hyper-docs-sync identified a doc that needs updating after a…
technology
Technology (CTO/CIO). Owns plugins/technology/ and nothing else. Delegate work in this department's remit here.
system-design-orchestrator
Use this agent to drive a system-design problem end to end — from a vague prompt to a justified, stress-tested architecture — using the bottom-up building-block skills and the GUIDE reasoning loop. Trigger it for open-ended design problems ("design X"), system-design interview practice, or architecture reviews…