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/flutter/agent-plugins/code-documentationnpx skills add flutter/agent-plugins --skill code-documentationgit clone --depth 1 https://github.com/flutter/agent-pluginsWhat 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.00056 | $0.00909 |
| Opus 5 | $0.00028 | $0.00454 |
| Sonnet 5 | $0.00011 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
code-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- code-documentation — 97% identical, 3 lines differ
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.
Code Documentation Skill
This skill provides comprehensive guidelines for documenting code, prioritizing user-centric writing, clarity, and consistency.
1. General Philosophy
- User-Centric: Write for the person using your API. If you had to look up how to use something, document it so others don't have to.
- Explain "Why": Explain why code exists and how to use it effectively, since the code signature already tells what it does.
- Be Concise: Omit fluff. Avoid merely restating the code name, as it is not helpful.
- Consistency: Use standard terminology and consistent formatting.
- Public APIs: Document all public APIs (classes, members, top-level functions) without exception.
- Code Samples: Strongly consider adding code samples to explain usage.
2. General Structure
Follow this general structure for documentation comments across languages:
- Summary Sentence: Start with a single-sentence summary on the first line, ending with a period.
- Blank Line: Follow the summary with a blank line.
- Details: Add paragraphs, code samples, or lists as needed to explain parameters, return values, exceptions, and behavior.
- Annotations: Place doc comments before any metadata annotations.
3. Writing Guidelines
Brevity & Style
- Avoid Fluff: Omit "This class...", "This method...", "Is used to...", "Note that...".
- Bad: "This method is used to calculate the total."
- Good: "Calculates the total."
- Third-Person Verbs: Start function/method docs with a third-person singular verb.
- Examples: "Returns...", "Calculates...", "Updates...", "Creates...".
- Noun Phrases: Start variable/property docs with a noun phrase.
- Examples: "The current color.", "A list of active users.".
- Booleans: Always start with "Whether" (or similar clear indicator).
- Good: "Whether this widget is enabled."
- Bad: "If this widget is enabled...", "True if...", "Flag to indicate...".
- Avoid Jargon: Use plain English unless the term is a widely accepted standard (e.g., "HTTP", "URL").
What ships with it
3 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 · 70 lines · 56 tokens per session scan A 9fbcf476ed9a
code-documentation is a skill published in the GitHub repository flutter/agent-plugins (2,895 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 56 tokens to every session and 909 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…