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 rhdh-spec-driven-schemagit 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/rhdh-spec-driven-schema)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-spec-driven-schema"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-spec-driven-schema.svg" alt="Measured on agentmods" 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.00228 | $0.01231 |
| Opus 5 | $0.00114 | $0.00616 |
| Sonnet 5 | $0.00046 | $0.00246 |
| Haiku 4.5 | $0.00023 | $0.00123 |
Grade A, and why
rhdh-spec-driven-schema 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH spec-driven schema
Give every openspec-* skill one shared place to read the actual RHDH workflow definition, instead of each restating the schema's rules from memory.
What this skill owns
config.yaml— the project-local schema selection (rhdh-spec-driven), the RHDH context block (split canonical model, journal obligation), and the per-artifact house rules.schemas/rhdh-spec-driven/schema.yaml— the authoritative artifact graph:proposal -> {specs, design} -> tasks -> apply, each artifact's instruction text, and theapplyblock's direct-vs-team mode guidance.schemas/rhdh-spec-driven/templates/{proposal,spec,design,tasks}.md— the structural template for each artifact.- references/artifact-loop.md — the shared
mechanics for driving
openspec instructions <id> --change <name> --jsonand turning its response into a written artifact file. scripts/install_project_schema.py— copiesconfig.yamlandschemas/rhdh-spec-driven/into a product repo'sopenspec/so the OpenSpec CLI can resolve the schema there.
Install into the product repo (startup / setup)
OpenSpec loads schemas from the project's openspec/, not from this skill
directory. Before any openspec new change that should use rhdh-spec-driven,
ensure those files are on disk:
python3 scripts/install_project_schema.py
Run that from the product repo (or pass the project root as the first
argument). The helper lives next to this skill — resolve
scripts/install_project_schema.py relative to this skill's install path, not
under the product repo's scripts/. Use --force only when deliberately
replacing a customized copy.
Callers (/openspec-new-change, /openspec-ff-change, /openspec-onboard,
and /setup-rhdh-skills when seeding a product checkout) check for
openspec/config.yaml and openspec/schemas/rhdh-spec-driven/ first and run
this install step only when either is missing. Idempotent: existing files are
kept unless --force is set.
Writing into the product repo is an external write — take it through
/mutation-gate when the caller is in a setup or multi-operation plan; a
single scaffold turn that already creates openspec/changes/ may include this
copy in the same stated set.
What ships with it
9 files 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.
- agents/openai.yaml 156 B
- config.yaml 3.4 KB
- references/artifact-loop.md 1.9 KB
- schemas/rhdh-spec-driven/schema.yaml 11 KB
- schemas/rhdh-spec-driven/templates/design.md 473 B
- schemas/rhdh-spec-driven/templates/proposal.md 1.1 KB
- schemas/rhdh-spec-driven/templates/spec.md 199 B
- schemas/rhdh-spec-driven/templates/tasks.md 266 B
- scripts/install_project_schema.py 3.1 KB runs code
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.
- 8d ago First seen · 100 lines · 228 tokens per session scan A 9fd59181ba55
rhdh-spec-driven-schema is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 4d ago), licensed Apache-2.0. It adds 228 tokens to every session and 1,231 once invoked, about $0.0011 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…