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/neeeophytee/agent-stylebooks/github-docsnpx skills add Neeeophytee/agent-stylebooks --skill github-docsgit clone --depth 1 https://github.com/Neeeophytee/agent-stylebooksWhat 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.00057 | $0.00661 |
| Opus 5 | $0.00028 | $0.00331 |
| Sonnet 5 | $0.00011 | $0.00132 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
github-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 2d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub docs
Help developers complete a product workflow with accurate, approachable guidance.
Establish the contract
- Preserve commands, UI labels, permissions, plan or product availability, code, versions, and security consequences.
- Do not claim a feature exists for a plan, host, or version without evidence.
- Distinguish a supported workflow from a workaround or community convention.
- Surface missing facts as review questions.
Design the page
- Name the reader's goal in the title and opening.
- State prerequisites, permissions, supported environments, and risks before the reader reaches a dependent action.
- Give only enough concept to make the action understandable and safe.
- Present the shortest supported path first. Place alternatives in separate sections.
- Close the loop with verification, troubleshooting, or a useful next step.
Write for developers
- Address the reader as
youand keep the tone calm and collaborative. - Use active voice and concrete verbs. Name the component that performs an automatic action.
- Define product-specific terms on first use and keep terminology stable.
- Put the most important qualifier near the claim it limits.
- Explain why a step matters when the reason affects security, data, or the choice between alternatives.
- Use inclusive language and examples that do not assume geography, identity, or a single development environment.
- Separate normative instructions from optional suggestions.
Write procedures
- Begin steps with imperative verbs and use one main action per step.
- State the location before the control when the reader must navigate to it.
- Keep commands copyable. Explain substitutions and show the expected output only when it helps verify success.
- Put warnings directly before irreversible or security-sensitive actions.
- Offer recovery paths that state what data or configuration may change.
Make the page scannable
- Use sentence case and front-load meaningful words in headings.
- Use descriptive link text instead of generic destinations.
- Use numbered lists for sequences, bullets for options, and tables for repeated comparisons with the same fields.
- Use backticks for code and literal technical elements. Use bold for visible UI labels.
- Keep notes exceptional. Move essential information into the main flow.
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.
- 2d ago First seen · 74 lines · 57 tokens per session scan A 28b2e1693377
github-docs is a skill published in the GitHub repository Neeeophytee/agent-stylebooks (54 stars, last pushed 9d ago), licensed MIT. It adds 57 tokens to every session and 661 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
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.
golden-rss
Use when testing the rss golden build.
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"…
agy-delegate
Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use…
pre-modification-check
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.