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-find)<a href="https://agentmods.dev/commands/stahldavid/sensegrep/sensegrep-find"><img src="https://agentmods.dev/badge/commands/stahldavid/sensegrep/sensegrep-find.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.00008 | $0.00184 |
| Opus 5 | $0.00004 | $0.00092 |
| Sonnet 5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
sensegrep-find 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 8d 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
Use mcp__plugin_sensegrep_sensegrep__sensegrep_search to answer the user request.
Execution rules:
- Treat
$ARGUMENTSas the semantic query. If empty, ask for a query before calling tools. - Start with a broad call using only
queryandlimit=20. - If results are noisy, refine with one or more of:
symbolType,language,include,isAsync,isExported,minComplexity,pattern. - Return concise findings with clickable file paths and why each result is relevant.
- If no results are found, suggest one narrower and one broader follow-up query.
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.
- 8d ago First seen · 15 lines · 8 tokens per session scan A 784187d648ec
sensegrep-find is a command published in the GitHub repository Stahldavid/sensegrep (1 stars, last pushed 23d ago), licensed Apache-2.0. It adds 8 tokens to every session and 184 once invoked, about $0.0000 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
rb-setup
A first-time setup command for RepoBrain, a tool that lets an agent ask questions about a codebase and refresh its codebase knowledge. It configures either an API-key service or a local command-line agent that is already signed in.
rb-ask
A command for asking questions about the current codebase through RepoBrain, a code knowledge tool.
rb-refresh
A command that rebuilds RepoBrain's knowledge base for the current workspace. RepoBrain is a tool that keeps searchable project information for an agent.
file
Read a file (whole or a line range) from an external cix project's server-side checkout.
tree
List a directory (one level) in an external cix project's server-side checkout.
init
Initialize the cix index for the current project (registers, indexes, starts file watcher).