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 instructions/redhat-developer/rhdh-skills/agents-mdgit 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/instructions/redhat-developer/rhdh-skills/agents-md)<a href="https://agentmods.dev/instructions/redhat-developer/rhdh-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/redhat-developer/rhdh-skills/agents-md.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 | $0.02162 | $0.02162 |
| Opus 5 | $0.01081 | $0.01081 |
| Sonnet 5 | $0.00432 | $0.00432 |
| Haiku 4.5 | $0.00216 | $0.00216 |
Grade A, and why
rhdh-skills AGENTS.md 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 3d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Agent Skills for Red Hat Developer Hub engineering, operations, and repository
maintenance. Skills follow the Agent Skills open standard. Read CONTEXT.md
for domain language and docs/adr/ for architectural decisions.
1. Think Before Coding
Do not assume or hide confusion.
- State assumptions explicitly.
- Surface multiple interpretations and tradeoffs.
- Prefer the simpler approach when it satisfies the request.
- Stop and ask when ambiguity would materially change the result.
2. Simplicity First
Write the minimum code that solves the requested problem.
- Add no speculative features or single-use abstractions.
- Keep CLI implementation stdlib-only except for the documented PEP 723 YAML exception in ADR-0002.
- If a change can be substantially smaller without losing behavior, simplify it.
3. Surgical Changes
Touch only what the request requires. Preserve unrelated work and match the existing style. Remove only the imports, variables, functions, or files made obsolete by your own change.
4. Goal-Driven Execution
Translate the request into observable success criteria and verify them. Run
uv run pytest before reporting repository work complete.
When any .py file changed, ship Python that already matches CI. Run ruff
after editing, and again before committing, opening a pull request, or
reporting work complete. Tests passing is not enough — ruff check is not
ruff format --check.
uv run ruff format <changed.py> ...
uv run ruff check <changed.py> ...
CI (lint job) runs the same tools across the tree:
uv run ruff check .
uv run ruff format --check .
Format and check. Fix findings, rerun until both pass, then include those
files in the same commit. Prefer ruff's quote style (single quotes when the
string contains "). Do not open a pull request until both pass.
5. No Irreversible Commands Without Confirmation
Never force-push, reset HEAD, merge branches, or run destructive commands without explicit confirmation.
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.
- 3d ago First seen · 216 lines · 2,162 tokens per session scan A b6f1bb8ff559
rhdh-skills AGENTS.md is an instructions file published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed today), licensed Apache-2.0. It adds 2,162 tokens to every session, about $0.0108 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.