What is red-hat-docs?

A guide for writing modular Red Hat-style technical documentation. It focuses on precise administration, installation, configuration, security, troubleshooting, procedures, concepts, and references.

Use it to draft or review enterprise documentation for setup, administration, configuration, security, troubleshooting, and product references.

It helps make prerequisites, system state, actions, supported configurations, and verification steps clear without promising behaviour that has not been established.

red-hat-docs — Skill for Claude Code and Codex by Neeeophytee

Install

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.

Any agent

npx skills add Neeeophytee/agent-stylebooks --skill red-hat-docs

Clone the repo

git clone --depth 1 https://github.com/Neeeophytee/agent-stylebooks

Made for: Claude Code, Codex.

Or install agent-stylebooks, the plugin that ships this one along with the rest of its 16 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/neeeophytee/agent-stylebooks/red-hat-docs/github.svg)](https://agentmods.dev/skills/neeeophytee/agent-stylebooks/red-hat-docs)

Your own site

<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 639 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00024	$0.00256
Sonnet 5.5	$0.00012	$0.00128
Haiku 4.5	$0.00006	$0.00064

Measured 2mo ago against content hash 611f25d7acb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

skills/red-hat-docs/SKILL.md · 70 lines

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 you only 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.

Read the full file on GitHub · 70 lines

Files

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.

Changes

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.

2mo ago First seen · 70 lines · 61 tokens per session scan A 611f25d7acb0

Subscribe to this mod's changes

red-hat-docs is a skill published in the GitHub repository Neeeophytee/agent-stylebooks (78 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 639 once invoked, about $0.0002 per session on Opus 5.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.

Claude Code Writing and docs agent-skills content-design documentation gemini-cli openai-codex

red-hat-docs next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
red-hat-docsNeeeophytee/agent-stylebooks	Skill	78	2mo ago	MIT	A	61	Claude Code, Codex
readmethuanvd378/write-me-a-readme	Skill	2	3mo ago	MIT	A	103	Claude Code, Codex
yapperdzan314/yapper	Skill	1	6mo ago	MIT	A	54	Claude Code, Codex
spec-kitty-charter-doctrinePriivacy-ai/spec-kitty	Skill	1.7k	19d ago	MIT	A	135	Claude Code, Codex
mongodb-query-optimizerfcakyon/claude-codex-settings	Skill	1.2k	yesterday	Apache-2.0	A	98	Claude Code
chisle-auditJayPokale/Chisle	Skill	741	14d ago	MIT	A	130	Claude Code
crane-shotcafe3310/public-agent-skills	Skill	256	yesterday	Apache-2.0	A	25	Claude Code, Codex