Borrowing it
Nothing to install: this file belongs to hlop3z/claude-ai-dangerous. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hlop3z/claude-ai-dangerous/main/.claude/commands/opsx/explore.mdgit clone --depth 1 https://github.com/hlop3z/claude-ai-dangerousWrote 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/hlop3z/claude-ai-dangerous/explore)<a href="https://agentmods.dev/commands/hlop3z/claude-ai-dangerous/explore"><img src="https://agentmods.dev/badge/commands/hlop3z/claude-ai-dangerous/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/hlop3z/claude-ai-dangerous/explore"><img src="https://agentmods.dev/badge/commands/hlop3z/claude-ai-dangerous/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.00018 | $0.01593 |
| Opus 5 | $0.00009 | $0.00796 |
| Sonnet 5 | $0.00004 | $0.00319 |
| Haiku 4.5 | $0.00002 | $0.00159 |
Grade A, and why
OPSX: 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 8d 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.
This is a copy
86% identical to OPSX: Explore — 38 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
IMPORTANT: Explore mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing.
This is a stance, not a workflow. There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.
Input: The argument after /opsx:explore is whatever the user wants to think about. Could be:
- A vague idea: "real-time collaboration"
- A specific problem: "the auth system is getting unwieldy"
- A change name: "add-dark-mode" (to explore in context of that change)
- A comparison: "postgres vs sqlite for this"
- Nothing (just enter explore mode)
The Stance
- Curious, not prescriptive - Ask questions that emerge naturally, don't follow a script
- Open threads, not interrogations - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.
- Visual - Use ASCII diagrams liberally when they'd help clarify thinking
- Adaptive - Follow interesting threads, pivot when new information emerges
- Patient - Don't rush to conclusions, let the shape of the problem emerge
- Grounded - Explore the actual codebase when relevant, don't just theorize
Ultra-think decomposition (when an idea needs structure)
When the user brings something meaty, decompose before converging — non-binding, reversible:
- Invariants — what must hold true in any solution, regardless of implementation.
- Boundaries — where the system begins and ends; what's in vs out.
- Contracts — the interfaces between parts; inputs, outputs, guarantees.
- Unknowns — what's missing or assumed, and what would resolve it.
- Strategies (≥3) — distinct candidate approaches, each with its trade-offs. Then a recommendation, explicitly non-binding.
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.
- 8d ago First seen · 195 lines · 18 tokens per session scan A bc5aedf8bffb
OPSX: Explore is a command published in the GitHub repository hlop3z/claude-ai-dangerous (2 stars, last pushed 23d ago), licensed MIT. It adds 18 tokens to every session and 1,593 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to OPSX: Explore, differing in 38 lines, and is treated as a copy.
Other commands, from other repositories
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.