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/dwmkerr/claude-toolkit/exploration-protocolnpx skills add dwmkerr/claude-toolkit --skill exploration-protocolgit clone --depth 1 https://github.com/dwmkerr/claude-toolkitWrote 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/dwmkerr/claude-toolkit/exploration-protocol)<a href="https://agentmods.dev/skills/dwmkerr/claude-toolkit/exploration-protocol"><img src="https://agentmods.dev/badge/skills/dwmkerr/claude-toolkit/exploration-protocol.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.00060 | $0.00625 |
| Opus 5 | $0.00030 | $0.00313 |
| Sonnet 5 | $0.00012 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
exploration-protocol scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| API returns 401 on bad auth | `curl -H "Auth: bad"` shows 401 | How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exploration Protocol
A structured approach to explore features before production development. The goal is to learn, build acceptance criteria, experiment with verifiable prototypes, and codify learnings.
Task Folder Structure
tasks/NNN-taskname/
├── 01-objectives.md
├── 02-acceptance-criteria.md
├── 03-architecture.md
├── 04-verifiable-prototype.md
├── 05-verification.md
├── 06-outcome.md
├── 99-research/
└── 99-findings/
Document Templates
You MUST read the template files in ./references/001-example-task/ before scaffolding a task folder. These templates show the exact structure and format to use:
- 01-objectives.md
- 02-acceptance-criteria.md
- 03-architecture.md
- 04-verifiable-prototype.md
- 05-verification.md
- 06-outcome.md
Key Patterns
Stub Markers
For sections to be filled in later:
> Stub - to be filled in after objectives and acceptance criteria are approved.
Criteria Tables
Always pair criteria with verification method:
| Criterion | Verification Method |
|-----------|---------------------|
| User can log in | Manual test: complete flow, see logged-in state |
| API returns 401 on bad auth | `curl -H "Auth: bad"` shows 401 |
Checkpoint Lists
For prototypes, use checkboxes:
**Checkpoint 1:**
- [ ] Auth0 application configured
- [ ] PKCE enabled
ASCII Diagrams
Keep simple:
┌─────────────┐ ┌─────────────┐
│ Popup │────▶│ Background │────▶ API
└─────────────┘ └─────────────┘
Phase Flow
- Objectives → user reviews
- Acceptance Criteria → user approves before work begins
- Architecture → stub until criteria approved
- Prototype → incremental with checkpoints
- Verification → evidence for each criterion
- Outcome → learnings and follow-on work
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/001-example-task/01-objectives.md 1.1 KB
- references/001-example-task/02-acceptance-criteria.md 1.1 KB
- references/001-example-task/03-architecture.md 1.3 KB
- references/001-example-task/04-verifiable-prototype.md 584 B
- references/001-example-task/05-verification.md 782 B
- references/001-example-task/06-outcome.md 374 B
- skill-tests.yaml 714 B
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.
- 6d ago First seen · 85 lines · 60 tokens per session scan A c57363b04c98
exploration-protocol is a skill published in the GitHub repository dwmkerr/claude-toolkit (23 stars, last pushed 11d ago), licensed MIT. It adds 60 tokens to every session and 625 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…