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/Stahldavid/sensegrepWrote 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/stahldavid/sensegrep/sensegrep-health)<a href="https://agentmods.dev/commands/stahldavid/sensegrep/sensegrep-health"><img src="https://agentmods.dev/badge/commands/stahldavid/sensegrep/sensegrep-health/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/commands/stahldavid/sensegrep/sensegrep-health"><img src="https://agentmods.dev/badge/commands/stahldavid/sensegrep/sensegrep-health.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.00010 | $0.00170 |
| Opus 5 | $0.00005 | $0.00085 |
| Sonnet 5 | $0.00002 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
sensegrep-health 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 11d 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
Run this sequence:
- Call
mcp__plugin_sensegrep_sensegrep__sensegrep_indexwithaction: "stats". - Inspect index readiness, file/chunk counts, provider metadata, and freshness fields when present.
- If the user explicitly needs language inventory or language variants, tell them that this is intentionally CLI-only and suggest
sensegrep languages --detectorsensegrep languages --variants.
Report:
- Index readiness and any obvious issues.
- Suggested search filters based on the user's target area, when obvious.
- One next action to improve search quality, such as indexing incrementally or scoping with
include.
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.
- 11d ago First seen · 16 lines · 10 tokens per session scan A a4010a74fdb1
sensegrep-health is a command published in the GitHub repository Stahldavid/sensegrep (1 stars, last pushed 26d ago), licensed Apache-2.0. It adds 10 tokens to every session and 170 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-31.
Other commands, from other repositories
search
Semantic code search via cix — find code by meaning, not by exact strings.
def
Find symbol definition(s) via cix — go-to-definition across the indexed codebase.
refs
Find symbol references via cix — locate every usage of a symbol across the codebase.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
fire-resurrect
Autonomous Resurrection Mode — reverse-engineer intent from messy code, then rebuild clean from scratch.
fire-reflect
After any failure (debug resolution, test failure, approach rotation, stalled loop), capture what was tried, why it failed, and what actually worked as a persistent reflection. Future sessions search these before investigating.