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/dgouron/review-flow/create-docnpx skills add DGouron/review-flow --skill create-docgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/create-doc)<a href="https://agentmods.dev/skills/dgouron/review-flow/create-doc"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/create-doc.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00021 | $0.00566 |
| Opus 5 | $0.00010 | $0.00283 |
| Sonnet 5 | $0.00004 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
create-doc 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 5d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Documentation
Activation
This skill activates for:
- Creating a new documentation file
- Documenting a feature, a concept, or a component
/create-doc
Persona
Read .claude/roles/documentalist.md — adopt this profile and follow all its rules.
Workflow
Step 1: Clarify the Subject
If the subject is vague, ask:
- Which component/feature to document?
- Target audience: contributor, user, LLM?
- Scope:
reference,guide,architecture, orspec?
Step 2: Detect Duplicates
MANDATORY before any creation.
# List all existing docs
Glob docs/**/*.md
# Read the titles and H2/H3 of each file
# Compare with the requested subject
If an existing doc already covers the subject:
- STOP — do not create a new file
- Suggest updating the existing doc via
/update-docs - Explain which file covers what
If partial overlap:
- Identify precisely which sections already exist
- The new doc must cover ONLY the missing content
- Add links to existing sections
Step 3: Create the File
Apply the template from PERSONA.md:
---
title: <Title>
scope: reference | guide | architecture | spec
related:
- src/path/to/source.ts
- docs/RELATED-DOC.md
last-updated: YYYY-MM-DD
---
Writing rules:
- English only
- 1-2 summary sentences after the title
- One section = one concept
- Tables rather than lists for structured data
- Code blocks rather than prose for technical details
- Max 800 words — split if longer
Step 4: Naming
| Location | Convention |
|---|---|
docs/ top-level |
SCREAMING-KEBAB.md (e.g., MCP-TOOLS-REFERENCE.md) |
| Subdirectory | kebab-case.md (e.g., docs/mcp/architecture.md) |
Step 5: Update the Index
Run /docs-index to regenerate docs/INDEX.md with the new file.
Anti-patterns
| Forbidden | Do Instead |
|---|---|
| Duplicate existing content | Link to the canonical source |
| Doc > 800 words | Split into multiple files |
| Sections unrelated to the title | Create a separate doc |
| Prose when a table suffices | Use a table |
| Mixing French and English | Everything in English |
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.
- 5d ago First seen · 93 lines · 21 tokens per session scan A 7e0b3648eb24
create-doc is a skill published in the GitHub repository DGouron/review-flow (42 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 566 once invoked, about $0.0001 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
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
verify-changes
Verify a code change in this repo before committing or opening a PR. Use after editing collector (backend), web (frontend), shared package, or the Go agent — picks the minimal sufficient check set per touched area.
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
monitor-webcams
Discover live webcams in a map viewport and resolve thumbnails or player URLs. Use when the user asks for visual context near a location, route, border, port, or city.
track-tariff-trends
Retrieve MFN applied tariff-rate timeseries for a reporting country — applied vs bound rates by year, plus the optional US effective tariff rate. Use when the user asks how a country's MFN tariffs have changed over time.
frontend-conventions
Frontend convention reference (SvelteKit / Svelte 5). Auto-injected into frontend-aware agents - not user-invocable.