What is aid-design-document?

A planning aid for deciding what kind of document to write, how it should be structured, who will read it, and where it belongs. It records the plan before the document is drafted.

Use it to plan a document’s audience, format, structure, angle, and location. It prepares a design for a separate writing step.

It helps clarify a document’s purpose and shape before writing begins, reducing unfocused drafts and misplaced content.

aid-design-document — Skill for Claude Code by AndreVianna

Install

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.

Any agent

npx skills add AndreVianna/aid-methodology --skill aid-design-document

Clone the repo

git clone --depth 1 https://github.com/AndreVianna/aid-methodology

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-document/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-document)

Your own site

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-document"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-document/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-document"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-document.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 151 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 970 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00151	$0.00970
Opus 5.5	$0.00060	$0.00388
Sonnet 5.5	$0.00030	$0.00194
Haiku 4.5	$0.00015	$0.00097

Measured 26d ago against content hash c4712aa26b58, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

aid-design-document 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 26d 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.

.agents/skills/aid-design-document/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Document (develop a design seed, resolve nothing)

Bind VERB=design, ARTIFACT=document -- the design stage in the contract's vocabulary -- then follow the shared contract at .aid/runtime/templates/design-lifecycle.md. This skill binds that contract and restates none of its rules. The seed it writes is .aid/design/document.md; realizing it into the written document is /aid-create-document's job, not this one's.

Boundary vs /aid-create-document: that skill writes the document from a ready seed; this one only develops the seed. Neither resolves anything on its own -- the user decides when a seed is ready to realize.
Boundary vs bare /aid-document: that skill writes a general document now; this one develops the document's direction as a reusable seed first. Design it here; write it there.
Not a numbered pipeline phase; does not route to /aid-execute.

State machine: INTAKE -> DESIGN -> VERIFY (loop) -> PRESENT [user decides] -> DONE, as design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose} entry line on each state.

State: INTAKE

Require a subject. Empty argument -> ask one bootstrapping question ("What document do you want to design -- its kind, structure, audience, and placement?") and wait.
Allocate through the Work Initiation Gate exactly as the contract's Allocation rule requires (.agents/skills/aid-design/SKILL.md INTAKE step 4 is the shape), with initiator: aid-design-document. phase is not driven.
Acquire .aid/design/ per the contract, then read .aid/design/document.md if a prior seed exists -- re-invocation iterates it rather than starting over.
Classify complexity for the aid-architect dispatch (verifier tier >= producer).

Advance: DESIGN.

State: DESIGN

Dispatch aid-architect (clean context, tiered) to write or iterate .aid/design/document.md in the seed shape the contract fixes (design-seed.md; feature-002 §4), grounded in .aid/knowledge/ and the project source plus any seed read in INTAKE. What this artifact's seed must settle: the document's kind and structure, its audience, and its placement; its ## Destination names where the written document lands. Never writes .aid/knowledge/ and never writes production code -- the design invariant (design-lifecycle.md).

Read the full file on GitHub · 89 lines

Changes

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.

26d ago Changed c4712aa26b58
2mo ago First seen · 89 lines · 151 tokens per session scan A 0db5db002c7b

Subscribe to this mod's changes

aid-design-document is a skill published in the GitHub repository AndreVianna/aid-methodology (6 stars, last pushed 11d ago), licensed MIT. It adds 151 tokens to every session and 970 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.

Documents Planning

aid-design-document next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
aid-design-documentAndreVianna/aid-methodology	Skill	6	11d ago	MIT	A	151	Claude Code
orbit-notionnexu-io/open-design	Skill	107k	today	Apache-2.0	A	117	Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-plugins	Skill	35k	yesterday	Apache-2.0	A	123	Claude Code
apify-youtube-transcript-scrapersickn33/agentic-awesome-skills	Skill	49k	yesterday	MIT	A	48	Claude Code
legal-holdanthropics/claude-for-legal	Skill	9.9k	yesterday	Apache-2.0	A	68	Claude Code
report-to-pdfasgeirtj/system_prompts_leaks	Skill	71k	yesterday	CC0-1.0	A	17	Claude Code, Codex
artifact-template-minimal-letterheadasgeirtj/system_prompts_leaks	Skill	71k	yesterday	CC0-1.0	A	54	Claude Code, Codex