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-continue-changegit 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-continue-change)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/openspec-continue-change"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-continue-change/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-continue-change"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-continue-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.00598 |
| Opus 5.5 | $0.00034 | $0.00239 |
| Sonnet 5.5 | $0.00017 | $0.00120 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
openspec-continue-change 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continue an OpenSpec change
Create one artifact — the next one whose dependencies are satisfied — and stop, so the user reviews each step before the next is generated.
Steps
-
Select the change. If not named or inferable from context, run
openspec list --jsonand ask the user to pick from the most recently modified 3-4 changes, marking the most recent as "(Recommended)". Never guess. -
Check status:
openspec status --change "<name>" --jsonRead
schemaName,artifacts[].status, andisComplete. Specs and design each depend only on proposal — when both areready, pick one (either order is valid); do not treat YAML list order as a hard dependency. -
Act on status:
- All complete (
isComplete: true) — congratulate, show final status, suggest implementing (/openspec-apply-change) or archiving (/openspec-archive-change). Stop. - An artifact is
ready— pick one ready artifact and create it by following the artifact creation loop in/rhdh-spec-driven-schema. Create exactly one artifact, then stop. - Nothing is ready and nothing is complete — this should not happen with a valid schema; show status and suggest checking for a schema issue.
- All complete (
-
Show progress:
openspec status --change "<name>".
Output
After each invocation: which artifact was created, the schema in use, current progress (N/M complete), and what is now unlocked. Close with: "Want to continue? Just ask me to continue or tell me what to do next."
Guardrails
- Create exactly one artifact per invocation — never more.
- Never skip required dependencies; when multiple artifacts are ready (specs and design after proposal), either order is fine.
- If context for the artifact is unclear, ask before creating it.
Completion
Complete when exactly one artifact was written (verified to exist on disk) and the user has seen updated progress and what it unlocked — or, if already complete, when that state was reported without attempting a write.
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 · 63 lines · 86 tokens per session scan A 98a3c7fc450c
openspec-continue-change is a skill published in the GitHub repository redhat-developer/rhdh-skills (18 stars, last pushed today), licensed Apache-2.0. It adds 86 tokens to every session and 598 once invoked, about $0.0003 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…