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 Neeeophytee/agent-stylebooks --skill red-hat-docsgit clone --depth 1 https://github.com/Neeeophytee/agent-stylebooksWrote 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/neeeophytee/agent-stylebooks/red-hat-docs)<a href="https://agentmods.dev/skills/neeeophytee/agent-stylebooks/red-hat-docs"><img src="https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/red-hat-docs.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.00061 | $0.00639 |
| Opus 5 | $0.00030 | $0.00319 |
| Sonnet 5 | $0.00012 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
red-hat-docs 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red Hat docs
Create modular enterprise documentation that makes prerequisites, system state, actions, and verification explicit.
Preserve product accuracy
- Keep product names, versions, commands, files, paths, options, UI labels, and supported configurations exact.
- Do not generalize a tested configuration into universal support.
- Separate required, recommended, optional, deprecated, and unsupported behavior.
- Ask for missing privilege, platform, version, and persistence facts.
Build one module at a time
Choose one dominant module type:
- Concept: provide the mental model and relationships needed for later decisions.
- Procedure: state prerequisites, perform one goal-directed sequence, and verify it.
- Reference: present facts, options, syntax, or limits in a consistent lookup form.
- Troubleshooting: identify a symptom, diagnostic evidence, cause, and recovery.
Do not mix several independent goals in one procedure. Link modules into a larger assembly when a workflow needs multiple goals.
Write direct technical prose
- Address the reader as
youonly when they act. Name the system or component when it acts. - Prefer active voice and concrete verbs. Avoid hiding actions inside abstract nouns.
- Keep terminology stable and match authoritative product capitalization.
- Put a condition before an instruction when the reader must check it first.
- State scope: host, cluster, namespace, user, service, session, or persistent configuration.
- Use literal, globally understandable language and define unfamiliar abbreviations.
- State security and data consequences without alarmism or euphemism.
Write a procedure
- Give the goal in one sentence.
- List prerequisites, permissions, and starting state.
- Start each step with an imperative verb and keep one main action per step.
- Show commands and configuration exactly. Explain placeholders and variables.
- State the expected result where it helps the reader continue safely.
- Add a verification section with an observable success condition.
- Add reversal, cleanup, or recovery when the change is persistent or risky.
What ships with it
2 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.
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 · 70 lines · 61 tokens per session scan A 611f25d7acb0
red-hat-docs is a skill published in the GitHub repository Neeeophytee/agent-stylebooks (58 stars, last pushed 15d ago), licensed MIT. It adds 61 tokens to every session and 639 once invoked, about $0.0003 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
ciel-documentation-engine
CIEL's framework for high-integrity documentation generation, validation, and semantic indexing.
readme
Create, redesign, audit, or update a repository README.md by inspecting the actual project; write accurate setup and usage guidance with a selectable brand voice, polished information architecture, evidence-based badges and claims, discoverability suggestions, and an optional editable SVG/PNG banner. Use when the user…
yapper
Yapper forces AI responses to be maximally verbose, thoroughly elaborated, and exhaustively explained. All output is expanded by 200–400%. Technical accuracy is maintained at 100%. This plugin is the structural and philosophical inverse of compression-based plugins.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.