Borrowing it
Nothing to install: this file belongs to DesignPipe/exfig. 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/DesignPipe/exfig/main/.claude/skills/openspec-explore/SKILL.mdgit clone --depth 1 https://github.com/DesignPipe/exfigWrote 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/designpipe/exfig/openspec-explore)<a href="https://agentmods.dev/skills/designpipe/exfig/openspec-explore"><img src="https://agentmods.dev/badge/skills/designpipe/exfig/openspec-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/skills/designpipe/exfig/openspec-explore"><img src="https://agentmods.dev/badge/skills/designpipe/exfig/openspec-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.00039 | $0.02157 |
| Opus 5.5 | $0.00016 | $0.00863 |
| Sonnet 5.5 | $0.00008 | $0.00431 |
| Haiku 4.5 | $0.00004 | $0.00216 |
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 1mo 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
88% identical to openspec-explore — 47 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 — 291 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 (e.g., start a change with /opsx:new or /opsx:ff). 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.
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
What You Might Do
Depending on what the user brings, you might:
Explore the problem space
- Ask clarifying questions that emerge from what they said
- Challenge assumptions
- Reframe the problem
- Find analogies
Investigate the codebase
- Map existing architecture relevant to the discussion
- Find integration points
- Identify patterns already in use
- Surface hidden complexity
Compare options
- Brainstorm multiple approaches
- Build comparison tables
- Sketch tradeoffs
- Recommend a path (if asked)
Visualize
┌─────────────────────────────────────────┐
│ Use ASCII diagrams liberally │
├─────────────────────────────────────────┤
│ │
│ ┌────────┐ ┌────────┐ │
│ │ State │────────▶│ State │ │
│ │ A │ │ B │ │
│ └────────┘ └────────┘ │
│ │
│ System diagrams, state machines, │
│ data flows, architecture sketches, │
│ dependency graphs, comparison tables │
│ │
└─────────────────────────────────────────┘
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.
- 1mo ago First seen · 291 lines · 39 tokens per session scan A 64ded43c11f4
openspec-explore is a skill published in the GitHub repository DesignPipe/exfig (10 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 2,157 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to openspec-explore, differing in 47 lines, and is treated as a copy.
Other skills, from other repositories
design-qa
A visual checking and correction workflow that compares a running app screen with its Figma source using captures, overlays, difference maps, and pixel measurements. An overlay places two images together so mismatches are easier to see.
design-to-ui
A workflow for turning Figma designs into native Android or iOS screens. Figma is a design tool; native output means Android Jetpack Compose or XML, and iOS SwiftUI or UIKit code that runs on those platforms.
figma-diff-apply
A workflow for applying only the changed parts of a Figma design to code on a design branch. A design branch is a separate code version used for review before changes are merged.
figma-asset-download
A skill that downloads icons and images from a selected Figma frame as SVG or PNG files through Figma's web interface. SVG is a scalable format for vector artwork, while PNG is a raster image format.
generate-project-design-system
A draft generator that studies a project's code and Figma design data to prepare a design-system skill. A design system is a shared set of colors, sizes, components, and usage rules for keeping interfaces consistent.
argent-lens
Propose multiple visual design variants for on-screen elements and let the human pick in the Argent Lens window. Use when the user asks for design alternatives / options / A-B choices for a screen or component, or any time you have produced more than one candidate look for an element and want a human decision before…