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 skills add m3data/sense-mcp --skill sensegit clone --depth 1 https://github.com/m3data/sense-mcpWrote 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/m3data/sense-mcp/sense)<a href="https://agentmods.dev/skills/m3data/sense-mcp/sense"><img src="https://agentmods.dev/badge/skills/m3data/sense-mcp/sense/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/skills/m3data/sense-mcp/sense"><img src="https://agentmods.dev/badge/skills/m3data/sense-mcp/sense.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.00021 | $0.00375 |
| Opus 5.5 | $0.00008 | $0.00150 |
| Sonnet 5.5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
sense 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 2mo 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
Sense Search
Search the indexed ecosystem using the sense_search MCP tool.
With arguments
Parse $ARGUMENTS as follows:
- The main text is the search query
--project <name>filters to a specific project--type <source_type>filters by type (trace, documentation, project_claude, reference, research, teaching, code)--limit <n>sets max results (default 10)--mode <mode>overrides Vibe Harness mode for search shaping (explore, build, think-with, ship, cool-off, none). Omit to auto-detect. Usenoneto force flat cosine search regardless of Vibe Harness state.
Examples:
/sense how does authentication work/sense API error handling --project backend/sense deployment configuration --type documentation --limit 5/sense architecture decisions --mode explore
Without arguments
When $ARGUMENTS is empty, synthesize a search query from the conversation context:
- Review the last 3-5 exchanges in the current conversation
- Identify the core topic, concepts, or question being discussed
- Compose a 3-8 word query that captures the semantic thread
- Prefix results with "Searching for: [synthesized query]" so the user sees what was searched
- Call
sense_searchwith the synthesized query
This enables mid-conversation discovery — just type /sense to surface related prior work without crafting a query.
General
Call sense_search with the parsed arguments and display the results. If the index is empty, suggest running /sense-sync first.
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.
- 2mo ago First seen · 40 lines · 21 tokens per session scan A c18091f2d681
sense is a skill published in the GitHub repository m3data/sense-mcp (1 stars, last pushed 12d ago), licensed Apache-2.0. It adds 21 tokens to every session and 375 once invoked, about $0.0001 per session on Opus 5.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.
sense compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sensem3data/sense-mcp | Skill | 1 | 12d ago | Apache-2.0 | A | 21 | Claude Code |
| code_explorergoogle-gemini/gemini-cli | Skill | 109k | today | Apache-2.0 | A | 28 | Gemini CLI |
| qualitygoogle-gemini/gemini-cli | Skill | 109k | today | Apache-2.0 | B | 24 | Gemini CLI |
| agentcore-investigationawslabs/mcp | Skill | 9.9k | yesterday | Apache-2.0 | A | 52 | Claude Code, Codex |
| amazon aurora dsqlawslabs/mcp | Skill | 9.9k | yesterday | Apache-2.0 | A | 46 | Claude Code |
| session-investigatorevalstate/fast-agent | Skill | 4.0k | today | Apache-2.0 | A | 68 | Claude Code, Codex |
| embeddings-searchericrisco/rsc-harness | Skill | 555 | 4d ago | MIT | A | 88 | Claude Code, Codex |