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 n-n-code/n-n-code-skills --skill design-md-authorgit clone --depth 1 https://github.com/n-n-code/n-n-code-skillsWrote 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/n-n-code/n-n-code-skills/design-md-author)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/design-md-author"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/design-md-author.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.1 | $0.00066 | $0.01176 |
| Opus 5 | $0.00033 | $0.00588 |
| Sonnet 5 | $0.00013 | $0.00235 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
design-md-author 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 today.
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design.md author
Give the next designer or implementer enough information to make a consistent choice. A useful document explains which rule applies, where it comes from, and when an exception is valid.
Agree on the deliverable through the request
| Requested activity | Deliver |
|---|---|
| Explain or review | Findings and supporting evidence in the conversation |
| Draft in chat | Proposed document text, with unresolved choices labeled |
| Create | A design reference at the selected product's document path |
| Update | A focused change that preserves the document's other decisions |
Read the relevant repository instructions and existing changes first. A file
called design.md may describe software architecture; use its contents and
the requested outcome to determine ownership. Use documenter for architecture
documentation and the appropriate UI skill when implementation is requested.
Honor a specified path. Otherwise find the existing document for the product,
including case variants and app-specific copies; for a new document default to
DESIGN.md at that product's root. Resolve a material product/path ambiguity
before writing. Preserve custom sections, casing, and unrelated user changes.
A design-document request supplies authority for the requested document work. Honor requested outline or section checkpoints, and reuse approvals already given for the work. It does not itself authorize redesigning the application, installing tools, exporting remote tokens, or changing how an agent loads project instructions.
Establish what the document can claim
Start with the product purpose, audience, supported platforms, existing document, and accepted design decisions. Find the relevant shared components, themes, tokens, assets, and representative screens. Read only the evidence needed for this scope; expand when a sample reveals conflicting variants.
Classify each material rule before presenting it:
| Basis | Treatment |
|---|---|
| Accepted product decision | State the rule and its applicable scope |
| Source declaration or observed interface | Describe what was found and under which conditions |
| Proposed direction | Identify it as a proposal and explain the decision it would resolve |
| Missing or conflicting evidence | State the gap; avoid manufacturing a value or rule |
What ships with it
4 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.
- today First seen · 117 lines · 66 tokens per session scan A 6a0509510220
design-md-author is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 1,176 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-09-06.
Other skills, from other repositories
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
review-a11y
Internal accessibility review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks the changed user-facing surface for accessibility: semantics, keyboard, focus, contrast, and ARIA correctness — applies only to user-facing surfaces. Findings only…
review-design
Internal UI/UX design review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks the changed UI against the project's design doc: consistency, states, responsiveness, and reuse — applies only when the project has a UI and the change touches it.…
web-frontend-designer
Scaffold frontend architecture, components, routing, and UI dependencies from project config and wireframes.
web-ux-architect
Generate sitemap and wireframe specifications from project-config.json and produce UX planning artifacts.
mermaid-diagrams
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes…