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 skills/mburdo/knowledge_and_vibes/explorenpx skills add Mburdo/knowledge_and_vibes --skill exploregit clone --depth 1 https://github.com/Mburdo/knowledge_and_vibesWrote 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/mburdo/knowledge_and_vibes/explore)<a href="https://agentmods.dev/skills/mburdo/knowledge_and_vibes/explore"><img src="https://agentmods.dev/badge/skills/mburdo/knowledge_and_vibes/explore.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 | $0.00044 | $0.00962 |
| Opus 5 | $0.00022 | $0.00481 |
| Sonnet 5 | $0.00009 | $0.00192 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
explore 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore — Codebase Discovery
Parallel codebase search. Runs 8 searches per turn for efficient discovery. Direct execution.
Design rationale: This skill executes directly as a simple MCP call, not substantial analytical work. The Warp-Grep MCP handles the complexity internally.
When This Applies
| Signal | Action |
|---|---|
| "How does X work?" | Use /explore |
| Data flow across files | Use /explore |
| Cross-cutting concerns | Use /explore |
| Understanding architecture | Use /explore |
| User says "/explore" | Run discovery |
How It Works
Warp-Grep is an MCP tool that activates automatically for natural language code questions. It:
- Interprets your question
- Runs up to 8 parallel searches
- Returns relevant code snippets with context
Tool Reference
The Warp-Grep MCP provides these capabilities:
| Capability | Description |
|---|---|
| Parallel search | Up to 8 searches per turn |
| Context-aware | Returns surrounding code |
| Natural language | Understands questions |
| Cross-file | Follows data flow |
Query Patterns
Good Queries
"How does the payment processing flow work?"
"Where are user sessions managed?"
"How is error handling done in the API layer?"
"What happens when a request comes in?"
"How do modules communicate?"
"What's the data flow for authentication?"
Less Effective Queries
| Query | Problem | Better Tool |
|---|---|---|
| "Find function X" | Too specific | Grep or rg |
| "Open file Y" | Not a search | Read tool |
| "Does X exist?" | Simple check | Glob |
When to Use /explore
| Use Case | Use /explore? |
|---|---|
| "How does authentication work?" | YES |
| Data flow analysis | YES |
| Understanding module interactions | YES |
| Finding all usages of a pattern | YES |
| Cross-cutting concern analysis | YES |
| Architecture understanding | YES |
When NOT to Use /explore
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.
- 4d ago First seen · 178 lines · 44 tokens per session scan A 69eb0d9b5969
explore is a skill published in the GitHub repository Mburdo/knowledge_and_vibes (44 stars, last pushed 8mo ago), licensed MIT. It adds 44 tokens to every session and 962 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…