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 skills add Avinava/document-design-system --skill writing-documentsgit clone --depth 1 https://github.com/Avinava/document-design-systemWrote 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/avinava/document-design-system/writing-documents)<a href="https://agentmods.dev/skills/avinava/document-design-system/writing-documents"><img src="https://agentmods.dev/badge/skills/avinava/document-design-system/writing-documents/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/avinava/document-design-system/writing-documents"><img src="https://agentmods.dev/badge/skills/avinava/document-design-system/writing-documents.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00141 | $0.02517 |
| Opus 5.5 | $0.00056 | $0.01007 |
| Sonnet 5.5 | $0.00028 | $0.00503 |
| Haiku 4.5 | $0.00014 | $0.00252 |
Grade A, and why
writing-documents 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 18d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Documents
A technical document exists to get a reader to a decision, or to a working understanding, without them having to reconstruct the author's thinking.
The failure mode is not ugliness. It is a document that is complete, accurate, and unreadable — where the reader cannot find the decision, cannot tell what is settled versus proposed, and cannot see what changed since they last read it.
This skill is two layers. Do not glue them together.
- Writing (default) — pick the shape (a type, or a composition from a pattern), write from evidence. Output is Markdown in the user's tree.
- Design system (opt-in) — tokens, themes, print, self-contained HTML. Load
core/only when the user asked for HTML, PDF, print, a designed page, or "use the design system".
Format first
format = markdown, unless the user asked for html, pdf, print, designed, themed, or "use the design system".
| Format | Load | Do not load |
|---|---|---|
markdown |
this file, the type file (or references/composing.md plus the nearest type's file), references/writing.md, references/evidence.md |
core/, themes, templates/longform.html, print.css, build_document.py |
html / pdf |
the above plus references/output.md and core/ |
— |
both |
Markdown first (canonical in-repo), then HTML from that source | — |
Full dial, conventional paths, and HTML assembly: references/output.md.
On the Markdown path, leave Mermaid as fenced blocks. Prerender to themed SVG only on the HTML path.
State the assumption in one line. Do not quiz.
Writing
docs/adr/adr-014.mdas typeadr(markdown). Designed HTML on request.
Ask only when the slug is actually ambiguous or the request conflicts with another skill. If they asked for HTML and named no theme, use the type file's default-theme. Do not quiz. field-notes is only a fallback when the type has not been resolved yet.
Never offer a designed HTML version unprompted.
Pick the shape
Type first; compose when none fits.
What ships with it
58 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.
- core/a11y.md 2.9 KB
- core/base.css 7.5 KB
- core/document-patterns.css 21 KB
- core/document-patterns.md 11 KB
- core/print.css 4.3 KB
- core/themes/brand-template.css 4.1 KB
- core/themes/console-violet.css 3.5 KB
- core/themes/editorial-coral.css 1.3 KB
- core/themes/executive-navy.css 1.0 KB
- core/themes/field-notes.css 1.0 KB
- core/themes/horizon.css 1.9 KB
- references/composing.md 3.5 KB
- references/consultancy-lifecycle.md 2.2 KB
- references/evidence.md 2.8 KB
- references/output.md 4.0 KB
- references/profile-mulesoft.md 1.5 KB
- references/suites.md 1.3 KB
- references/type-adr.md 1.8 KB
- references/type-api-contract.md 1.8 KB
- references/type-architecture.md 1.7 KB
- references/type-change-request.md 921 B
- references/type-delivery-plan.md 902 B
- references/type-design-doc.md 2.7 KB
- references/type-design-handoff.md 1.8 KB
- references/type-discovery.md 2.0 KB
- references/type-estimate.md 837 B
- references/type-explanation.md 1.1 KB
- references/type-handoff.md 2.0 KB
- references/type-how-to.md 1.1 KB
- references/type-incident-update.md 925 B
- references/type-index.md 7.4 KB
- references/type-migration-plan.md 951 B
- references/type-onboarding.md 1.4 KB
- references/type-postmortem.md 1.8 KB
- references/type-project-charter.md 1.0 KB
- references/type-proposal.md 1.5 KB
- references/type-readiness-review.md 987 B
- references/type-reference.md 1.2 KB
- references/type-release-notes.md 819 B
- references/type-requirements.md 1.1 KB
- references/type-risk-register.md 1.0 KB
- references/type-runbook.md 1.5 KB
- references/type-service-docs.md 1.2 KB
- references/type-spec.md 1.7 KB
- references/type-statement-of-work.md 983 B
- references/type-status-report.md 827 B
- references/type-support-model.md 885 B
- references/type-test-report.md 1.7 KB
- references/type-test-strategy.md 858 B
- references/type-threat-model.md 1.2 KB
- references/type-tutorial.md 1.3 KB
- references/type-workshop-summary.md 897 B
- references/writing.md 3.2 KB
- scripts/build_document.py 2.7 KB runs code
- scripts/export_pdf.mjs 4.2 KB runs code
- scripts/inline_fonts.py 4.3 KB runs code
- scripts/render_diagram.mjs 7.6 KB runs code
- templates/longform.html 1018 B
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.
- 18d ago Changed · +14 lines · +21 tokens per session d9931db0aab0
- 1mo ago Changed · +9 lines · -44 tokens per session c2d24d7be4ff
- 1mo ago First seen · 180 lines · 164 tokens per session scan A 942bdc3022cf
writing-documents is a skill published in the GitHub repository Avinava/document-design-system (2 stars, last pushed 19d ago), licensed MIT. It adds 141 tokens to every session and 2,517 once invoked, about $0.0006 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-31.
Other skills, from other repositories
ui-ux-audit
Audits web UI and raises it from competent to exceptional. Catches what AI tools ship and people notice at once: broken or shifting layouts, cards and values off a shared line, orphaned words and lone grid items, drifting radii, gutters, ratios and component sizes, text overflow, missing states, poor contrast, small…
ui-ux-laws
Priority-ordered rulebook of core UX/UI laws, cognitive-psychology principles, Nielsen's usability heuristics, and accessibility requirements that Claude must actively apply (not just cite) whenever it designs, builds, redesigns, reviews, or critiques any user interface — websites, web/mobile apps, dashboards, forms…
design-component
Design a UI component spec to the house quality bar (anatomy, variants, sizes, the 8 states, token mapping, and accessibility). Use when the user wants to design or document a component (button, input, tabs, toast, combobox, date picker, modal, etc.) at the spec level before or alongside code. For generating framework…
design-screen
Design or build a page, screen, landing page, website, app or UI from a request - the whole job, end to end. Use this for "design a landing page", "build a settings screen", "make me a website", "design the onboarding", "ออกแบบหน้าเว็บ", "ทำหน้า landing", "ออกแบบ UI", "ทำแอป". It runs the pipeline no single skill…
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
scaffold-project
Scaffold a new design-product project that matches the recommended Claude Code layout (the reference structure). Use when starting a fresh product/app that will be built with this design system.