What is aid-design-architecture?

A planning aid for defining a software system's structure. It records its parts, boundaries, interactions, rules that must always hold, and things intentionally left outside the design.

Use it to work out how components should be divided and communicate, including what the system deliberately will not contain.

It makes architectural decisions explicit before they are turned into the project's formal architecture document.

aid-design-architecture — 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-architecture

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-architecture/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-architecture)

Your own site

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

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

When invoked 1,214 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.00181	$0.01214
Opus 5.5	$0.00072	$0.00486
Sonnet 5.5	$0.00036	$0.00243
Haiku 4.5	$0.00018	$0.00121

Measured 26d ago against content hash 045718e3a204, 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-architecture 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-architecture/SKILL.md · 103 lines

How it starts

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

Design Architecture (develop a design seed, resolve nothing)

Bind VERB=design, ARTIFACT=architecture -- 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/architecture.md; realizing it into the project's C1 document is /aid-create-architecture's job, not this one's.

Boundary vs /aid-create-architecture: that skill realizes the seed into the C1 document; this one only develops the seed. Neither resolves anything on its own.
Boundary vs bare /aid-design and /aid-document-architecture: bare /aid-design is the catch-all for a subject with no dedicated row; /aid-document-architecture writes documentation about an architecture -- the opposite side of the KB write boundary.
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 system or subsystem do you want to design -- its components, boundaries, and invariants?") 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-architecture. phase is not driven.
Acquire .aid/design/ per the contract, then read .aid/design/architecture.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/architecture.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 components, their boundaries and interactions, the invariants, and what is deliberately NOT a component.

Read the full file on GitHub · 103 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 045718e3a204
2mo ago First seen · 103 lines · 181 tokens per session scan A 578c31146036

Subscribe to this mod's changes

aid-design-architecture is a skill published in the GitHub repository AndreVianna/aid-methodology (6 stars, last pushed 11d ago), licensed MIT. It adds 181 tokens to every session and 1,214 once invoked, about $0.0007 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.

Planning

aid-design-architecture next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
aid-design-architectureAndreVianna/aid-methodology	Skill	6	11d ago	MIT	A	181	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code