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 agentmods add skills/andrevianna/aid-methodology/aid-create-stacknpx skills add AndreVianna/aid-methodology --skill aid-create-stackgit 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-create-stack)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-create-stack"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-create-stack.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 | $0.00191 | $0.01985 |
| Opus 5 | $0.00096 | $0.00992 |
| Sonnet 5 | $0.00038 | $0.00397 |
| Haiku 4.5 | $0.00019 | $0.00198 |
Grade A, and why
aid-create-stack 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 5d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Stack (realize a seed into the C0 document)
Bind VERB=create, ARTIFACT=stack -- the create 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. It consumes the seed /aid-design-stack produces and touches
.aid/design/ for no other purpose.
- Boundary vs
/aid-update-stack: that skill revises C0 content this lifecycle already committed; this one realizes a seed. - Boundary vs
/aid-create-configand/aid-update-config: those act on a configuration option within a chosen stack; this one records the stack choice itself. - Not a numbered pipeline phase; does not route to
/aid-execute.
State machine: INTAKE -> CREATE -> VERIFY -> PRESENT -> DONE, as
design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose} entry
line on each state.
State: INTAKE
- 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-create-stack.phaseis not driven. - Read the seed at
.aid/design/stack.md. - Resolve the destination by concern, not filename. This skill binds concern C0
(technology,
.claude/aid/templates/kb-authoring/concern-model.md). The seed's## Destinationnames the resolved path; where it does not, resolve C0 against.aid/settings.ymlknowledge.doc_set, falling back to the C0 row of.claude/aid/templates/kb-authoring/domain-doc-matrix.md, and confirm with the user. An ambiguous realization is asked, never picked silently. The seed also names a second destination -- the project's D document, for the rejected alternatives. - Read the whole destination if it exists, and note its
source:field. - 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.
- 5d ago First seen · 175 lines · 191 tokens per session scan A 237db8b878ed
aid-create-stack is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed yesterday), licensed MIT. It adds 191 tokens to every session and 1,985 once invoked, about $0.0010 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
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…