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/chhuax/praxis-devos/openspec-explorenpx skills add chhuax/praxis-devos --skill openspec-exploregit clone --depth 1 https://github.com/chhuax/praxis-devosWrote 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/chhuax/praxis-devos/openspec-explore)<a href="https://agentmods.dev/skills/chhuax/praxis-devos/openspec-explore"><img src="https://agentmods.dev/badge/skills/chhuax/praxis-devos/openspec-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.00047 | $0.01191 |
| Opus 5 | $0.00023 | $0.00596 |
| Sonnet 5 | $0.00009 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
openspec-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enter exploration mode. The goal is to converge on the problem, boundaries, constraints, and approaches clearly rather than implementing code directly.
Exploration mode is for thinking, not implementation. You may read files, search code, and investigate the codebase. Only write conclusions back into the current change's OpenSpec artifact when the user explicitly asks to capture them. Do not write business code or directly implement features.
Core Positioning
- OpenSpec owns change context, artifacts, and existing decisions
- Superpowers owns requirement and solution convergence
openspec-exploreleads the exploration flow
Exact Skill Protocol
- When this route is matched, you must call the corresponding exact skill name
- Do not substitute a semantically similar local skill, default skill, manual steps, or long-form reasoning
- If the exact skill is unavailable, report that explicitly and do not silently fall back
Brainstorming Gate
In openspec-explore, superpowers:brainstorming is not an optional enhancement. It is the default convergence capability.
If the current exploration involves any of the following, you must actually invoke superpowers:brainstorming first:
- A new feature or capability direction
- Option comparison and design tradeoff decisions
- Scope convergence for proposal, specs, or design
- Breaking vague requirements into a viable change
- Returning to design-level discussion within an existing change
This call can be lightweight, but it must really happen. Do not skip it with reasons such as "the direction is already clear," "we can write the proposal/design directly," or "we can draft the artifact first and brainstorm later."
The convergence call must satisfy these 4 rules:
- Actually load and use
superpowers:brainstorming; do not merely claim in text that brainstorming already happened - Use it only as the convergence capability for the current explore stage, without entering its own spec, plan, or implementation workflow
- Do not produce
docs/superpowers/**or any other side-channel spec or plan documents - After the call completes, return to
openspec-explorefirst, then decide whether to keep exploring, recommend/opsx:proposeoropenspec-new-change, or write back to the current change artifact only when the user explicitly asks to capture
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.
- 4d ago First seen · 110 lines · 47 tokens per session scan A 652eb090721c
openspec-explore is a skill published in the GitHub repository chhuax/praxis-devos (21 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,191 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…