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-sync-specsgit 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-sync-specs)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/openspec-sync-specs"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-sync-specs/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-sync-specs"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-sync-specs.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.00653 |
| Opus 5.5 | $0.00035 | $0.00261 |
| Sonnet 5.5 | $0.00018 | $0.00131 |
| Haiku 4.5 | $0.00009 | $0.00065 |
Grade A, and why
openspec-sync-specs 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync delta specs to main specs
Read delta specs and directly edit main specs to apply their intent — allowing partial updates like adding one scenario without copying an entire requirement.
Steps
- Select the change. If not given, run
openspec list --json, show changes that have delta specs underspecs/, and let the user choose. Never guess. - Find delta specs at
openspec/changes/<name>/specs/*/spec.md. Each may contain## ADDED Requirements,## MODIFIED Requirements,## REMOVED Requirements,## RENAMED Requirements(FROM:/TO: format). If none found, tell the user and stop. - For each capability with a delta spec, read both the delta and the
main spec at
openspec/specs/<capability>/spec.md(may not exist yet), then apply intelligently:- ADDED — add if new; if it already exists, update it to match (treat as an implicit MODIFIED).
- MODIFIED — find the requirement and apply the changes: add scenarios, modify existing ones, or change the description. Preserve content the delta doesn't mention.
- REMOVED — remove the entire requirement block.
- RENAMED — find the FROM requirement, rename to TO.
- If the capability has no main spec yet, create
openspec/specs/<capability>/spec.mdwith a Purpose section (brief, can be TBD) and the ADDED requirements.
- Show a summary: which capabilities were updated and what changed (added/modified/removed/renamed requirements).
Key principle: intelligent merging
The delta represents intent, not a wholesale replacement. To add a scenario, include just that scenario under MODIFIED — don't copy existing ones. Use judgment to merge sensibly; the operation should still be idempotent (running it twice gives the same result).
Guardrails
- Read both delta and main specs before changing anything.
- Preserve existing content the delta doesn't mention.
- Ask for clarification if intent is unclear rather than guessing.
- Show what's changing as you go.
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 · 64 lines · 88 tokens per session scan A 93064d1591e4
openspec-sync-specs 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 653 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…