Borrowing it
Nothing to install: this file belongs to kylebrodeur/mcp-network-analyzer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kylebrodeur/mcp-network-analyzer/main/.github/prompts/plan-searchExportedDataTool.prompt.mdgit clone --depth 1 https://github.com/kylebrodeur/mcp-network-analyzerWrote 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/kylebrodeur/mcp-network-analyzer/plan-searchexporteddatatool)<a href="https://agentmods.dev/commands/kylebrodeur/mcp-network-analyzer/plan-searchexporteddatatool"><img src="https://agentmods.dev/badge/commands/kylebrodeur/mcp-network-analyzer/plan-searchexporteddatatool/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/kylebrodeur/mcp-network-analyzer/plan-searchexporteddatatool"><img src="https://agentmods.dev/badge/commands/kylebrodeur/mcp-network-analyzer/plan-searchexporteddatatool.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.00000 | $0.00245 |
| Opus 5.5 | $0.00000 | $0.00098 |
| Sonnet 5.5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
plan-searchExportedDataTool 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 14d 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
Plan: Implement search_exported_data Tool
A complete search implementation that leverages the existing rich capture data, analysis results, and database infrastructure to provide powerful querying capabilities across all exported network traffic.
Steps
- Create search tool implementation in
src/tools/search.tswith query parsing, filtering logic, and result formatting - Enhance database service in
src/lib/database.tswith full-text search indexing and advanced filtering methods - Add content indexing to capture pipeline in
src/tools/capture.tsfor request/response body searchability - Update tool registration in
src/index.tsto wire the implemented search functionality - Add search result aggregation with grouping by domain, endpoint, status code, and content type
Further Considerations
- Search scope strategy: Should we index request bodies, response bodies, or both? Consider performance vs completeness tradeoffs
- Indexing approach: Use SQLite FTS5 for full-text search or implement simpler JSON-based filtering first?
- Result format: Return raw matches, summarized statistics, or both? How should large result sets be paginated?
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.
- 14d ago First seen · 18 lines · 0 tokens per session scan A 5fc55319b7b4
plan-searchExportedDataTool is a command published in the GitHub repository kylebrodeur/mcp-network-analyzer (1 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 245 tokens. 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-10-23.
plan-searchExportedDataTool compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| plan-searchExportedDataToolkylebrodeur/mcp-network-analyzer | Command | 1 | 15d ago | MIT | A | 0 | GitHub Copilot |
| vs-queuemtarcure/claude-vibe-squad | Command | 228 | 9d ago | MIT | A | 0 | Claude Code |
| vs-doctormtarcure/claude-vibe-squad | Command | 228 | 9d ago | MIT | A | 0 | Claude Code |
| vs-boardmtarcure/claude-vibe-squad | Command | 228 | 9d ago | MIT | A | 0 | Claude Code |
| vs-stopmtarcure/claude-vibe-squad | Command | 228 | 9d ago | MIT | A | 0 | Claude Code |
| fixHimanshu507/cgcone | Command | 9 | yesterday | MIT | A | 15 | Claude Code |
| testHimanshu507/cgcone | Command | 9 | yesterday | MIT | A | 11 | Claude Code |