A search and navigation guide for OpenSpec documents, which are project files describing features, requirements, and planned changes. It helps locate stable specifications, active changes, and archived work.

Use it to find specifications by topic, class, or file; list active changes; and read a capability's requirements or a change's proposal and design.

It avoids searching the project documentation blindly or missing the specification that defines a feature or code file.

opsx-search — Skill for Claude Code and Codex by grasscaograss

Install

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.

Any agent

npx skills add grasscaograss/AwesomeWeldoneSkills --skill opsx-search

Clone the repo

git clone --depth 1 https://github.com/grasscaograss/AwesomeWeldoneSkills

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin opsx-search — /plugin install opsx-search after adding the marketplace above.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/opsx-search/github.svg)](https://agentmods.dev/skills/grasscaograss/awesomeweldoneskills/opsx-search)

Your own site

<a href="https://agentmods.dev/skills/grasscaograss/awesomeweldoneskills/opsx-search"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/opsx-search/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/grasscaograss/awesomeweldoneskills/opsx-search"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/opsx-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 538 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00099	$0.00538
Opus 5	$0.00049	$0.00269
Sonnet 5	$0.00020	$0.00108
Haiku 4.5	$0.00010	$0.00054

Measured 12d ago against content hash 1aaa79fced5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

opsx-search 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 12d 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.

opsx-search/SKILL.md · 66 lines

What it actually says

OpenSpec Search

Search and navigate the project's OpenSpec documentation.

Directory Structure

openspec/
├── INDEX.md              # Capability index (READ THIS FIRST)
├── specs/<capability>/   # 78 stable capability specs
│   └── spec.md
├── changes/<change>/     # 17 active changes
│   ├── .openspec.yaml
│   ├── proposal.md       # Why / What / Impact
│   ├── design.md         # Decisions / Risks
│   ├── tasks.md          # Implementation checklist
│   └── specs/<cap>/spec.md  # Delta specs
└── changes/archive/      # 107 completed changes

Search Patterns

1. Quick lookup by topic

Read openspec/INDEX.md first. It groups all 78 capabilities by domain with one-line summaries.

2. Find specs mentioning a code file/class

grep -r "WeldUnrecognized" openspec/*/proposal.md openspec/specs/*/spec.md

3. Find specs by keyword

grep -ri "粗定位" openspec/specs/*/spec.md

4. List active changes with status

openspec list --json

5. Read a specific capability's full spec

openspec/specs/<capability-name>/spec.md

6. Read a change's motivation and impact

openspec/changes/<change-name>/proposal.md

Workflow

Start with INDEX.md — locate relevant capability names
Read the spec.md for detailed requirements and scenarios (BDD: WHEN/THEN)
Check proposal.md of related changes for motivation and code impact
Cross-reference — use grep to find connections between specs and code

Changes

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.

12d ago First seen · 66 lines · 99 tokens per session scan A 1aaa79fced5e

Subscribe to this mod's changes

opsx-search is a skill published in the GitHub repository grasscaograss/AwesomeWeldoneSkills (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 99 tokens to every session and 538 once invoked, about $0.0005 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-31.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens