Borrowing it
Nothing to install: this file belongs to extra-org/extra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/extra-org/extra/main/.claude/skills/documentation/SKILL.mdgit clone --depth 1 https://github.com/extra-org/extraWrote 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/extra-org/extra/documentation)<a href="https://agentmods.dev/skills/extra-org/extra/documentation"><img src="https://agentmods.dev/badge/skills/extra-org/extra/documentation/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.
<a href="https://agentmods.dev/skills/extra-org/extra/documentation"><img src="https://agentmods.dev/badge/skills/extra-org/extra/documentation.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.00805 |
| Opus 5.5 | $0.00013 | $0.00322 |
| Sonnet 5.5 | $0.00006 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
documentation 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Documentation
Purpose
Keep the repository's documentation accurate, honest, and synchronized with the code, so future agents and users can trust it.
When to Use This Skill
- Editing anything in
docs/, theREADME.md, orAGENTS.md. - Adding or changing an ADR.
- Shipping a behavior/contract change that documentation must reflect.
Files to Read First
AGENTS.mddocs/README.md(reading order and index).- The specific doc/ADR you are changing and any code it describes.
.ai/skills/skill-authoring.mdif the doc is a skill.
Core Principles
- Be honest about status. Clearly separate what exists from what is planned; use accurate status markers (✅ done / ⏳ planned).
- Never claim unimplemented features work. The project is in the foundation phase — don't describe the runtime/compiler/API as functioning.
- Docs follow code. Update docs in the same change as the behavior they describe; don't let them drift.
- Decisions go in ADRs. A binding architectural decision is recorded as an ADR, not buried in prose.
- Show, don't just tell. Prefer examples, flows, and small diagrams where they clarify.
- Right file for the right scope: README = user-facing; AGENTS.md =
repo-wide rules for agents; ADRs = architectural decisions;
docs/= design.
Process
- Identify scope. Decide which file(s) the change belongs in (README vs. AGENTS.md vs. docs vs. ADR) — don't scatter the same content.
- Write the change concisely; add an example or flow if it aids understanding.
- For a new binding decision, add
docs/adr/NNNN-title.mdusing the existing ADR format (Status, Context, Decision, Consequences, Alternatives, Enforcement). - Sync cross-references: update indexes (
docs/README.md,.ai/README.md) and any links. - Verify honesty: re-read for any claim that overstates current status.
- Validate with
make check.
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 · 87 lines · 32 tokens per session scan A 0a4e744404e9
documentation is a skill published in the GitHub repository extra-org/extra (117 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 805 once invoked, about $0.0001 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.
Other skills, from other repositories
skill-writing-plans
Create zero-context implementation plans with bite-sized tasks — use for multi-step feature planning.
argent-tv-interact
Control and inspect TV apps via argent, Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
agenticx-query-data-source
Use when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come from a live data source rather than training memory.
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
06-product-brief
Produces a concise Product Brief before requirements. Use when the user wants to frame or revisit a product opportunity and how it will be validated. Not for requirements, technical design, or planning.
issue-resolve
Use when an assessed gflow-cli issue (verdict CONFIRMED-BUG or LIKELY-BUG) has localized, verifiable scope and should be driven to a fix. Mutating and gated: it works in an isolated worktree, fixes test-first, and opens a DRAFT PR for human review. Built to run autonomously (hermes-ops) within a strict action envelope…