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-prototypegit 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-prototype)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-prototype"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-prototype/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-prototype"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-prototype.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.00141 | $0.01488 |
| Opus 5 | $0.00071 | $0.00744 |
| Sonnet 5 | $0.00028 | $0.00298 |
| Haiku 4.5 | $0.00014 | $0.00149 |
Grade A, and why
aid-prototype 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prototype (validate a direction, throwaway)
/aid-prototype builds a throwaway model now to de-risk a direction, captures the
validation signal, presents it, and hands the real build off. It resolves nothing and
its output is not production. For a design you intend to keep and build, use
/aid-design. Deeper per-slot guidance: .claude/aid/templates/shortcut-scaffolding/prototype.md.
- Not a numbered pipeline phase; does not route to
/aid-execute.
State machine: INTAKE -> BUILD -> VERIFY (light) -> PRESENT [user decides] -> HANDOFF? ->
DONE. Print the [State: NAME] -- {purpose} entry line on each state.
State: INTAKE
- Require a direction. Empty argument -> ask one bootstrapping question ("What direction do you want to validate, and what would tell you it works?") and wait.
- Capture (thin): direction/hypothesis; fidelity (
paper|low-fi|runnable spike, defaultlow-fi); the success signal that would validate it; the scope boundary (what it does NOT attempt -- keeps it throwaway). - Pick the path: Fast -- a clear direction + success signal -> build now. Guided -- vague ("prototype something for onboarding") -> scope direction / success signal / fidelity first.
- Classify complexity (model + effort): simple ->
aid-architectat sonnet / medium; complex (a runnable spike, a rich flow) -> opus / high. - Consult the Work Initiation Gate, then allocate the work folder + STATE. First run
the gate (
.claude/aid/templates/work-initiation-gate.md):bash .claude/aid/scripts/works/enumerate-works.sh(main tree + every git worktree). Empty -> allocate, no prompt. Works exist -> ask new-vs-continuation; on continuation route to the chosen work's resume door and STOP (allocate nothing); on new work: create and enter the worktree per the gate's§ 3astep 2 (worktree-lifecycle.sh create <work-id> <name>, STOP on a non-zero exit or empty path, else enter the resolved path), then allocate (pipeline.path: lite,initiator: aid-prototype,lifecycle: Running,active_skill: aid-prototype;phasenot driven). For a runnable spike, associate an opt-in git worktree so the throwaway code is isolated.
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 · 129 lines · 141 tokens per session scan A f711a1daf9eb
aid-prototype is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed yesterday), licensed MIT. It adds 141 tokens to every session and 1,488 once invoked, about $0.0007 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…