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/radix-ng/primitives/documentation-writingnpx skills add radix-ng/primitives --skill documentation-writinggit clone --depth 1 https://github.com/radix-ng/primitivesWrote 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/radix-ng/primitives/documentation-writing)<a href="https://agentmods.dev/skills/radix-ng/primitives/documentation-writing"><img src="https://agentmods.dev/badge/skills/radix-ng/primitives/documentation-writing.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.00096 | $0.01232 |
| Opus 5 | $0.00048 | $0.00616 |
| Sonnet 5 | $0.00019 | $0.00246 |
| Haiku 4.5 | $0.00010 | $0.00123 |
Grade A, and why
documentation-writing 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Management
Maintain project documentation in .claude/skills/project-knowledge/references/. Audit for bloat, edit files, check consistency, track status.
For creating documentation from scratch (new project or empty docs), use project-planning skill.
Documentation Principles
These rules apply to ALL documentation operations (audit, edit, create).
Goal: open docs → understand the project without reading code. What is this project, how it's structured, what it does, where to find key things, how to deploy, where are logs. A high-level navigation guide.
Describe what exists, what it does, and why. High-level overview of components, how they work together, decisions made (why this stack, why this architecture), operational details (server addresses, deploy procedures, log locations, env var names). Skip what's obvious from reading the code itself — function signatures, implementation details, generic framework behavior.
No code blocks, no pseudocode. Code in docs gets outdated and bloats context.
No duplication between files. Information lives in ONE place. Cross-reference: "See deployment.md for env vars."
patterns.md: only project-specific patterns. Universal coding standards. Project patterns.md contains only what's unique to THIS project.
File Structure
4 core files in .claude/skills/project-knowledge/references/:
| File | Contains |
|---|---|
| project.md | Overview, audience, problem, 3-5 key features, out of scope |
| architecture.md | Tech stack (with WHY), project structure, dependencies, integrations, data model |
| patterns.md | Project-specific code patterns, git workflow, testing methods, business rules |
| deployment.md | Platform, env var names, CI/CD triggers, rollback, monitoring |
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 · 113 lines · 96 tokens per session scan A 87852adc014d
documentation-writing is a skill published in the GitHub repository radix-ng/primitives (270 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 1,232 once invoked, about $0.0005 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
create-db-component
Creates a new DB UX Design System component with Mitosis source, SCSS, typed model, and Playwright tests.
modify-db-component
Modifies an existing DB UX Design System Mitosis component (add variants, update props, change styles).
test-component
Runs, analyzes, and fixes Playwright and accessibility tests for a specific DB UX component.
implement-component
Implements production-ready UI using DB UX Design System v3 components, tokens, and icons with a discovery-first approach.
migrate-to-v3
Migrates legacy DB UI v2 code (cmp-, elm-, rea- classes, Web Components, db-color- tokens) to DB UX Design System v3.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…