Borrowing it
Nothing to install: this file belongs to CaseyRo/mcp-mockuuups. 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/CaseyRo/mcp-mockuuups/main/.claude/skills/openspec-explore/SKILL.mdgit clone --depth 1 https://github.com/CaseyRo/mcp-mockuuupsWrote 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/caseyro/mcp-mockuuups/openspec-explore)<a href="https://agentmods.dev/skills/caseyro/mcp-mockuuups/openspec-explore"><img src="https://agentmods.dev/badge/skills/caseyro/mcp-mockuuups/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/caseyro/mcp-mockuuups/openspec-explore"><img src="https://agentmods.dev/badge/skills/caseyro/mcp-mockuuups/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.03265 |
| Opus 5.5 | $0.00016 | $0.01306 |
| Sonnet 5.5 | $0.00008 | $0.00653 |
| Haiku 4.5 | $0.00004 | $0.00327 |
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
91% identical to openspec-explore — 181 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 — 309 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. For a new change, scaffold it first as described below.
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.
Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context, schemas, view). Once selected, treat --store <id> as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run openspec status --change "<name>" --json --store "<id>", not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.
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 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 · 309 lines · 39 tokens per session scan A 8dca1ef60755
openspec-explore is a skill published in the GitHub repository CaseyRo/mcp-mockuuups (0 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 3,265 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to openspec-explore, differing in 181 lines, and is treated as a copy.
Other skills, from other repositories
swag
This skill should be used when the user says "add proxy config", "create reverse proxy", "SWAG config", "nginx proxy", "expose service", "proxy configuration", "subdomain config", "subfolder config", "configure SWAG", "list proxy configs", "view proxy config", "edit proxy config", "remove proxy config", "check proxy…
archivebox-kg-ingestion
Natively ingest an ArchiveBox archive into the epistemic-graph knowledge graph via the archivebox-api MCP server — push snapshots as typed :Snapshot nodes (with :Tag + :hasTag links and per-snapshot :Document page-text) and archive results as :ArchiveResult nodes, best-effort, with the Wire-First ingest tools. Use…
archivebox-snapshot-search
Browse and search an ArchiveBox archive via the archivebox-api MCP server — list/filter snapshots, read one snapshot (with its per-extractor archive results), list archive results by extractor/status, and read tags with the domain-typed core tool. Use when the agent must find an archived URL, inspect what was captured…
archivebox-web-archiving
Capture and re-archive web pages with ArchiveBox via the archivebox-api MCP server — add URLs (with tags, crawl depth, and chosen extractors), update / re-archive existing snapshots, and schedule recurring archiving with the domain-typed CLI tool. Use when the agent must permanently archive a URL, bulk-add a list of…
archivebox-api-operations
Operate archivebox-api through its governed MCP and Arbora capabilities, including archivebox kg ingestion, archivebox snapshot search, archivebox web archiving. Use when a request requires this provider's read, change, automation, ingestion, troubleshooting, or evidence workflows.
onenote
OneNote MCP connects an AI assistant to Microsoft OneNote through the Microsoft Graph API: browsing notebooks/sections/pages, reading full page content (HTML), creating and appending pages, and title + full-text search across the user's notes. 26 tools + 1 prompt (onenotetriage), dual transport (stdio + HTTP…