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-detailgit 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-detail)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-detail"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-detail/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-detail"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-detail.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.00104 | $0.01052 |
| Opus 5 | $0.00052 | $0.00526 |
| Sonnet 5 | $0.00021 | $0.00210 |
| Haiku 4.5 | $0.00010 | $0.00105 |
Grade A, and why
aid-detail 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detail — The Ultimate Breakdown
Break each deliverable from PLAN.md into small, sequential, testable tasks. Each task = one agent session = one reviewable unit = one human review.
⚠️ Pre-flight Checks
Check 1: Locate Work
- If arg provided → use that work directory
- If no arg → enumerate works cross-worktree: run
bash .claude/aid/scripts/works/enumerate-works.sh(main tree + every git worktree; never the local.aid/works/glob, which is empty onmaster), taking each record's field-1work_id - Single record → auto-select it
- Multiple records → list them, ask user to choose
- Zero records on any worktree → STOP. "No works found. Run
/aid-describefirst."
Locate + Enter the Work's Worktree
As soon as Check 1 resolves the work id and before Check 2 checks for
.aid/works/{work}/PLAN.md, follow .claude/aid/templates/downstream-worktree-entry.md to
normalize <work-id> to its bare work-NNN branch name, locate the worktree (which always
exits 0 and returns <path>\t<status>), and enter the returned path. Keep the defensive
empty-path/non-zero backstop that stops rather than operate blindly — it should not fire against
the real helper. Never create a new worktree — creation belongs to the work-starting skills only.
Check 2: Verify PLAN.md Exists
- Check for
.aid/works/{work}/PLAN.md - If missing → STOP. "No PLAN.md found. Run
/aid-planfirst."
Check 3: Verify Not in Plan Mode
- ✅
DefaultorAuto-accept edits→ Proceed. - ❌
Plan mode→ STOP.
State Detection
⚠️ FILESYSTEM IS THE ONLY SOURCE OF TRUTH. Always read actual files on disk.
- No
deliveries/delivery-NNN/tasks/task-NNN/DETAIL.mdexists under.aid/works/{work}/→ FIRST-RUN - At least one
deliveries/delivery-NNN/tasks/task-NNN/DETAIL.mdexists → REVIEW - Tasks complete and grade ≥ minimum → DONE
Print the state-entry line and "you are here" map:
FIRST-RUN:
[State: FIRST-RUN] — No task files yet; begin proposing task breakdown per deliverable.
aid-detail ▸ you are here
[● FIRST-RUN ] → [ REVIEW ] → [ DONE ]
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 96 lines · 104 tokens per session scan A 429dda302fb9
aid-detail is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed yesterday), licensed MIT. It adds 104 tokens to every session and 1,052 once invoked, about $0.0005 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…