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 agentmods add skills/redhat-developer/rhdh-skills/rhdh-contextnpx skills add redhat-developer/rhdh-skills --skill rhdh-contextgit 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-context)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/rhdh-context"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/rhdh-context.svg" alt="Measured on agentmods" 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.00218 | $0.01079 |
| Opus 5 | $0.00109 | $0.00540 |
| Sonnet 5 | $0.00044 | $0.00216 |
| Haiku 4.5 | $0.00022 | $0.00108 |
Grade A, and why
rhdh-context 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 6d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RHDH Context
The environment facts every other RHDH skill starts from: which repositories are checked out and where, which tools are on PATH, which RHDH and Backstage versions this checkout targets, and where its configuration lives. Callers invoke this skill by name and read what it reports; they never inspect its files or import its Python package.
What this skill hands back
Run this before another skill needs repository, tool, version, or configuration facts:
python scripts/context.py --project-root <repo> --json
It prints one JSON object and nothing else: repositories is an array of {name, path}, tools
maps each probed tool to installed, missing, or not-probed, and configuration carries the
config paths plus targetRhdh, targetBackstage, and source. The source is user when
--target-rhdh is given, repository when the checkout pins a version in backstage.json, and
rhdh-context when the answer comes from the checked-in compatibility matrix.
Consume the whole object. Reuse it within the session unless configuration or repository state
changes. When a required capability is missing, name that capability and tell the human to run
/setup-rhdh-skills; a model skill cannot invoke that human-only entry point.
Preserved CLI
Run the CLI from this skill directory as uv run scripts/rhdh <command>. It is a
bundled wrapper, not an installed executable: npx skills add copies skill
directories and installs no console script. The wrapper declares no
dependencies — the rhdh package beside it is stdlib-only.
| Outcome | Interface |
|---|---|
| Environment orientation and diagnostics | uv run scripts/rhdh status, uv run scripts/rhdh doctor |
| Layered project/user configuration | uv run scripts/rhdh config ... |
| Repository submodule setup | uv run scripts/rhdh setup submodule ... |
| Overlay workspace inspection | uv run scripts/rhdh workspace ... |
| Worklog state | uv run scripts/rhdh log ... |
| Todo state | uv run scripts/rhdh todo ... |
What ships with it
13 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 117 B
- references/rhdh-repos.md 35 KB
- references/versions.md 5.8 KB
- rhdh/__init__.py 434 B runs code
- rhdh/__main__.py 122 B runs code
- rhdh/cli.py 51 KB runs code
- rhdh/config.py 35 KB runs code
- rhdh/formatters.py 11 KB runs code
- rhdh/todo.py 9.8 KB runs code
- rhdh/worklog.py 4.6 KB runs code
- rhdh/workspace.py 3.4 KB runs code
- scripts/context.py 5.4 KB runs code
- scripts/rhdh 679 B
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.
- 6d ago First seen · 86 lines · 218 tokens per session scan A 86a0be4af685
rhdh-context is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 2d ago), licensed Apache-2.0. It adds 218 tokens to every session and 1,079 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-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…