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 commands/juanmhidalgo/claude-plugins/explore-plangit clone --depth 1 https://github.com/juanmhidalgo/claude-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/commands/juanmhidalgo/claude-plugins/explore-plan)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/explore-plan"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/explore-plan.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.00036 | $0.01561 |
| Opus 5 | $0.00018 | $0.00781 |
| Sonnet 5 | $0.00007 | $0.00312 |
| Haiku 4.5 | $0.00004 | $0.00156 |
Grade A, and why
explore-plan 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 today.
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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Repository: !
git remote get-url origin - Current branch: !
git branch --show-current - Feature: $ARGUMENTS
Phase 0: Resolve Feature and Validate
- Resolve the feature:
- If
$ARGUMENTSis provided → use it as the feature description. Recordsource_spec: null. - If
$ARGUMENTSis empty → auto-discover spec files. Use Glob with patternSPEC-*.mdin the repo root, then read each file's frontmatter and filter out any spec withstatus: implemented(those features are already shipped). From the remaining candidates:- 0 specs → STOP and ask the user for a feature description.
- 1 spec → use it. Read its frontmatter, use
feature:as the feature description, record the spec path assource_spec. Inform the user: "Auto-selected spec:SPEC-<slug>.md(feature: , status: )". Ifstatus: draft, also warn: "This spec is still in draft — the user may not have approved it yet. Proceed anyway?" and wait for confirmation. - 2+ specs → use AskUserQuestion to let the user pick (label =
feature:value, description =<filename> — status: <status>). Use the chosen spec'sfeature:as the feature description and record its path assource_spec.
- If
- Parse the feature into a one-line summary for agent prompts.
- Generate a plan filename:
PLAN-<slug>.md(slug = lowercase, hyphenated, max 4 words from the feature name. E.g.,PLAN-scheduled-notifications.md). Ifsource_specis set, reuse itsslug:value for consistency.
Phase 1: Explore and Generate Plan (Forked)
Launch a single Agent with subagent_type: "general-purpose" to do all exploration and plan generation in an isolated context.
CRITICAL: The agent MUST write the plan file to disk. The agent's context is discarded after it completes — only the file persists.
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.
- today First seen · 169 lines · 36 tokens per session scan A 5a5b978dc399
explore-plan is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 9d ago), licensed MIT. It adds 36 tokens to every session and 1,561 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-09-03.
Other commands, from other repositories
v-dispatch
Execute a Compound-V-ready plan, manifest, or run-id via batched parallel multi-backend dispatch. Accepts a bare plan path (auto-materializes the manifest), or a manifest|run-id (dispatches directly). Runs partition-reviewer first; on PASS dispatches Task 0 serially then the parallel batches, enforces the scope gate…
sruja-bugfix-triage
Systematic workflow for triaging and fixing bugs with architecture grounding.
triage
AI-powered reachability triage for dependency vulnerabilities. Scans for CVEs then searches your source code to estimate whether each vulnerable API is actually called. Outputs a prioritized FOUNDINSOURCE / UNCERTAIN / NOTFOUNDINGREP report.
readme-restructure
Execute a /readme-audit blueprint. Rewrites the README to the evaluator → conversion → links structure and creates linked docs by extracting and reorganising existing content.
smart-help
Context-aware help that suggests relevant commands.
check
Universal pre-flight check that validates project readiness.