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 AndreVianna/aid-methodology --skill aid-design-documentgit clone --depth 1 https://github.com/AndreVianna/aid-methodologyWrote 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/andrevianna/aid-methodology/aid-design-document)<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.
<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>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.00977 |
| Opus 5 | $0.00076 | $0.00489 |
| Sonnet 5 | $0.00030 | $0.00195 |
| Haiku 4.5 | $0.00015 | $0.00098 |
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 10d 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 — 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
.claude/aid/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 (
.claude/skills/aid-design/SKILL.mdINTAKE step 4 is the shape), withinitiator: aid-design-document.phaseis not driven. - Acquire
.aid/design/per the contract, then read.aid/design/document.mdif a prior seed exists -- re-invocation iterates it rather than starting over. - Classify complexity for the
aid-architectdispatch (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).
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.
- 10d ago First seen · 89 lines · 151 tokens per session scan A 0db5db002c7b
aid-design-document is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed today), licensed MIT. It adds 151 tokens to every session and 977 once invoked, about $0.0008 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-31.
Other skills, from other repositories
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
overleaf-sync
A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.