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.
git 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)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/explore"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/explore/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/juanmhidalgo/claude-plugins/explore"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/explore.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.00044 | $0.00563 |
| Opus 5.5 | $0.00018 | $0.00225 |
| Sonnet 5.5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
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 23d 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
Codebase Exploration
Deep dive into a specific topic in this codebase.
Topic: $ARGUMENTS
Exploration Strategy
- Entry points - Where does this topic get triggered/used?
- Core implementation - Main files that implement this functionality
- Data flow - How does data move through this feature?
- Dependencies - What does this rely on? What relies on it?
- Configuration - Any settings or env vars related to this?
- Tests - How is this tested? What can tests teach us?
Follow the topic into its callers, config, and tests, not just files whose names match.
Output Format
<output_format> Structure the findings as:
# Exploration: [Topic]
## Summary
[2-3 sentence overview of how this works in the codebase]
## Key Files
| File | Purpose | Key Functions/Classes |
|------|---------|----------------------|
| `path/to/file.py` | Description | `function_name`, `ClassName` |
## How It Works
1. [Step 1 of the flow] - `file:line`
2. [Step 2 of the flow] - `file:line`
3. [Step 3 of the flow] - `file:line`
## Code Examples
### [Example 1: Common usage]
```[language]
// From file:line
[relevant code snippet]
Related Areas
- [Related topic 1] - found in
path/to/files - [Related topic 2] - found in
path/to/files
Questions to Investigate Further
- [Things that weren't clear or need deeper exploration]
</output_format>
<critical_rules>
<rule priority="blocking">
Always include file:line references for every finding.
</rule>
<rule priority="blocking">
Show actual code snippets, not just descriptions.
</rule>
<rule priority="recommended">
If the topic is broad, suggest sub-topics to explore separately.
</rule>
</critical_rules>
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.
- 23d ago Changed b51e0de79622
- 1mo ago First seen · 91 lines · 44 tokens per session scan A ec17bca1f59e
explore is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 563 once invoked, about $0.0002 per session on Opus 5.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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.