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/skill-authoringnpx skills add redhat-developer/rhdh-skills --skill skill-authoringgit 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/skill-authoring)<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/skill-authoring"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/skill-authoring.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.00108 | $0.01398 |
| Opus 5 | $0.00054 | $0.00699 |
| Sonnet 5 | $0.00022 | $0.00280 |
| Haiku 4.5 | $0.00011 | $0.00140 |
Grade A, and why
skill-authoring 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Authoring
Create predictable Agent Skills through progressive disclosure, strong context pointers, checkable completion criteria, and single-sourced behavior.
Principles
- One skill per trigger phrase. A skill claims one thing a user would say. Two skills that would answer the same utterance are one skill; one skill that answers several unrelated utterances is several skills.
- Split by verb, never by noun. Verbs route; nouns collide.
createandrefineare two skills. Feature, Epic, and Story are one skill that infers the type, because the user often does not know which they want. - Weight the split by what a misroute costs. Merge where a misroute produces a wrong write; split where it produces an obvious wrong answer. A read-only misroute is visible immediately; a wrong mutation is not.
- A skill needing a disambiguating sub-command is two skills. If the body opens by asking which mode the user wants, the router should have decided.
- Keep every-branch steps in
SKILL.md; disclose branch-only reference behind a pointer that says when to read it. - Keep references one level deep and independently usable.
- Keep descriptions below 1024 characters and skill bodies below 500 lines.
The body limit governs
SKILL.mdonly — measure the whole directory too, and settle it with the question the line count only hints at: which of these vocabularies does a caller have to learn? One trigger phrase commits the caller to one. Two skills in this pack reached 4,029 and 7,784 total lines while theirSKILL.mdfiles stayed comfortably compliant. - Put deterministic validation and transformation in scripts.
Duplication
Judge it by layer, not by volume.
Prompt duplication is forbidden. When the same instructions, protocol, or domain rule would appear in two skills: extract a reference skill when nothing owns it, enforce the existing interface when a module already does, or document it once when it is a rule rather than a capability. Two callers is the threshold for extracting; one caller means it belongs inside its owner.
What ships with it
12 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 112 B
- references/anti-patterns.md 9.2 KB
- references/api-skill-patterns.md 6.0 KB
- references/architecture-patterns.md 17 KB
- references/audit.md 5.6 KB
- references/consolidation-guide.md 10 KB
- references/create.md 20 KB
- references/description-guide.md 2.8 KB
- references/scripts-guide.md 5.7 KB
- references/skill-quality.md 2.9 KB
- references/spec-guide.md 9.3 KB
- templates/simple-skill.md 997 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 · 122 lines · 108 tokens per session scan A b0fc00b0dac6
skill-authoring is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 2d ago), licensed Apache-2.0. It adds 108 tokens to every session and 1,398 once invoked, about $0.0005 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…
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…
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…
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…