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-update-architecturegit 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-update-architecture)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-update-architecture"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-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.
<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-update-architecture"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-architecture.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.00162 | $0.01574 |
| Opus 5 | $0.00081 | $0.00787 |
| Sonnet 5 | $0.00032 | $0.00315 |
| Haiku 4.5 | $0.00016 | $0.00157 |
Grade A, and why
aid-update-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 8d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Architecture (revise the C1 document)
Bind VERB=update, ARTIFACT=architecture -- the update 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.
- Boundary vs
/aid-create-architecture: that skill realizes a seed and owns the creation path; this one is the maintenance verb. Where the destination is absent this skill routes there rather than standing one up itself. - Boundary vs
/aid-document-architecture: that skill writes documentation about an architecture; this one revises the Knowledge Base record. - Not a numbered pipeline phase; does not route to
/aid-execute.
State machine: INTAKE -> UPDATE -> VERIFY -> PRESENT -> DONE, as
design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose} entry
line on each state.
State: INTAKE
- Require a stated change. Empty argument -> ask one bootstrapping question ("What should change in the architecture record?") 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-update-architecture.phaseis not driven. - No seed is required. The change stated in this run is a sufficient input, and this
skill completes without a seed. Read and consume one when present at
.aid/design/architecture.md, carrying its## Current directioninto the destination and deleting it once realized. - Resolve the destination by concern. This skill binds concern C1 (build & shape).
Where a seed supplied a
## Destination, use it; otherwise apply the concern rule here -- resolve C1 against.aid/settings.ymlknowledge.doc_set, falling back to the C1 row of.claude/aid/templates/kb-authoring/domain-doc-matrix.md-- and confirm the resolution with the user before writing. Never resolve silently. C1's default set holds bothproject-structure.mdandarchitecture.md; this skill targets the document describing the system's shape, neverproject-structure.md. - Read the whole destination, and note its
source:field. Absent destination -> route to/aid-create-architectureand write nothing. - Classify complexity for the
aid-architectdispatch (verifier tier >= producer).
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.
- 8d ago First seen · 146 lines · 162 tokens per session scan A 88d99c79a330
aid-update-architecture is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 2d ago), licensed MIT. It adds 162 tokens to every session and 1,574 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…