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 skills add redhat-developer/rhdh-skills --skill openspec-exploregit clone --depth 1 https://github.com/redhat-developer/rhdh-skillsWrote 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/redhat-developer/rhdh-skills/openspec-explore)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/openspec-explore"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/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/redhat-developer/rhdh-skills/openspec-explore"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/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.00088 | $0.00951 |
| Opus 5.5 | $0.00035 | $0.00380 |
| Sonnet 5.5 | $0.00018 | $0.00190 |
| Haiku 4.5 | $0.00009 | $0.00095 |
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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore mode
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
Explore mode is for thinking, not implementing. Read files, search code,
investigate the codebase — but never write code or implement features. If the
user asks to implement something, remind them to exit explore mode and use
/openspec-ff-change first. Creating OpenSpec artifacts
when explicitly asked is fine — that captures thinking, it does not implement
it.
This is a stance, not a workflow. No fixed steps, no required sequence, no mandatory output.
The stance
- Curious, not prescriptive — let questions emerge naturally; don't run a script.
- Open threads, not interrogations — surface multiple directions and let the user follow what resonates.
- Visual — use ASCII diagrams liberally when they clarify thinking.
- Adaptive — follow interesting threads, pivot on new information.
- Patient — let the shape of the problem emerge; don't rush conclusions.
- Grounded — explore the actual codebase rather than theorizing.
What you might do
Explore the problem space (ask emergent clarifying questions, challenge assumptions, reframe, find analogies), investigate the codebase (map architecture, find integration points, surface hidden complexity), compare options (brainstorm, build comparison tables, sketch tradeoffs, recommend a path if asked), and visualize freely — state diagrams, data flows, architecture sketches, dependency graphs, comparison tables.
OpenSpec awareness
Use OpenSpec context naturally, don't force it.
At the start, check openspec list --json for active changes, their schemas,
and status, to sense what the user might be working on.
When no change exists: think freely. When insight crystallizes, offer —
without pressure — "This feels solid enough to start a change. Want me to
create a proposal with /openspec-ff-change?"
When a change exists: read its artifacts for context
(openspec/changes/<name>/proposal.md, design.md, tasks.md, etc.) and
reference them naturally ("Your design mentions Redis, but SQLite fits
better now..."). Offer to capture crystallized insight where it belongs —
new/changed requirement in specs/<capability>/spec.md, design decision in
design.md, scope change in proposal.md, new work in tasks.md — then let
the user decide. Never auto-capture.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 98 lines · 88 tokens per session scan A 6684576cbb5d
openspec-explore is a skill published in the GitHub repository redhat-developer/rhdh-skills (18 stars, last pushed today), licensed Apache-2.0. It adds 88 tokens to every session and 951 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…