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/melodic-software/claude-code-plugins/explorenpx skills add melodic-software/claude-code-plugins --skill exploregit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/melodic-software/claude-code-plugins/explore)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/explore"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/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.00189 | $0.06161 |
| Opus 5 | $0.00095 | $0.03080 |
| Sonnet 5 | $0.00038 | $0.01232 |
| Haiku 4.5 | $0.00019 | $0.00616 |
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 yesterday.
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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-computed context
Current branch: !git branch --show-current 2>/dev/null || echo "unknown"
Working tree status (empty = clean): !{ git status --porcelain 2>/dev/null || echo "(git status unavailable)"; } | head -20
Project root: !git rev-parse --show-toplevel 2>/dev/null || echo "unknown"
These values orient this session only. The project root is an absolute machine path. Use it to resolve files while working, but never echo it into EXPLORE.md; the handoff artifact records relative paths (see the outcome gate below).
Routing. Dispatch by default
From the main conversation, this skill dispatches the discovery:explorer subagent. Exploration reads many files; keeping that out of the orchestrator's context window is the point. The agent loads the project's path-scoped rules, runs the six dimensions, writes the artifact set, and returns a bounded summary plus a file pointer, not the reads. The parent resolves the pre-dispatch envelope first, six fields (scope, reason, memory-slice path, memory root, budget, capability flags), written into the dispatch prompt as the labelled template in ${CLAUDE_PLUGIN_ROOT}/reference/parent-contract.md, not as prose the agent has to parse, and owns the post-dispatch boundary after: re-surfacing open_questions to the user, dispatching the sibling verifier, and writing its verdict back into EXPLORE.md, the explorer always returns verification: pending because it may not grade its own work, so an artifact left saying pending after the parent verified it cannot be told apart from one whose verifier never ran, and this artifact is the whole handoff a fresh session resumes from.
Run inline instead when any of these holds. Inline runs the identical workflow, and the escape hatch relaxes nothing:
- Tight turn-by-turn iteration. ≤~5 known files, findings feeding a same-session edit, and you will redirect as results land.
- Cost, a dispatched run pays the full six dimensions every time; a single-file question does not need an envelope.
- The invoking context is already a subagent. Dispatch-by-default is scoped to the main-conversation boundary. Hoisting, not nesting: the outer dispatch already supplied the fresh context, so a second hop only spends the inner agent's own window.
What ships with it
3 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.
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.
- yesterday First seen · 225 lines · 189 tokens per session scan A e8f7169842e0
explore is a skill published in the GitHub repository melodic-software/claude-code-plugins (15 stars, last pushed today), licensed MIT. It adds 189 tokens to every session and 6,161 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
generate-tree-structure
For tree/maze generation: spanning trees, random mazes, graph coverage. Uses frontier-based exploration with configurable traversal order.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
use-class-for-state
For complex state: encapsulate multiple interacting variables, stateful algorithms, backtracking search state.