aid-discover

aid-discover is a skill for Claude Code from AndreVianna/aid-methodology. It costs 118 tokens per session (5,595 once invoked), scanned A, original, MIT.

A codebase discovery tool that studies an existing repository and records its architecture, conventions, and patterns in a structured knowledge base.

In plain words
What is it for?
Use it when taking over an existing codebase or preparing it for planned changes, documentation, or further development.
Why use it?
It gives later work an evidence-based understanding of an unfamiliar project instead of relying on guesses about how the code works.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is raw="$(bash .claude/aid/scripts/config/read-setting.sh \.

Good fit Use it when taking over an existing codebase or preparing it for planned changes, documentation, or further development.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/AndreVianna/aid-methodology
agentmods
npx agentmods add skills/andrevianna/aid-methodology/aid-discover

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.

agentmods badge for aid-discover

README.md
[![agentmods](https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-discover/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-discover)
Your own site
<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-discover"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-discover/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.

agentmods 80×15 button for aid-discover

Your own site · 80×15
<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-discover"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-discover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,595 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00118 $0.05595
Opus 5 $0.00059 $0.02797
Sonnet 5 $0.00024 $0.01119
Haiku 4.5 $0.00012 $0.00560

Measured 8d ago against content hash db80ab3eef6a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

aid-discover 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.

.claude/skills/aid-discover/SKILL.md · 387 lines

How it starts

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

Brownfield Project Discovery

Analyze an existing project repository — all code, configuration, and documentation — and produce a structured .aid/knowledge/ directory by orchestrating 5 specialized discovery subagents. Includes a built-in quality gate that reviews, grades, and fixes KB documents.

State machine — each /aid-discover invocation drives the state machine until it hits a natural pause point per .claude/aid/templates/state-machine-chaining.md. Mechanical states and inline-question states auto-chain; only PAUSE-FOR-USER-ACTION, PAUSE-FOR-USER-DECISION, and HALT stop the run.


⛔ PRIME DIRECTIVE: NO ASSUMPTIONS — DEFER TO THE USER

This rule governs every state, every sub-agent, and the orchestrator itself. It overrides convenience, speed, and confidence.

Discovery's job is to report what the project actually is, never what an agent guesses it is. So whenever ANYTHING is unclear, ambiguous, contradictory, or a judgment call — an undefinable term, a discrepancy between two sources, an uncertain classification, which of two things is authoritative, in-or-out-of-scope, how to resolve a conflict — DO NOT resolve it by assumption. Record a question and DEFER the decision to the user.

  • A LIKELY / UNCERTAIN / probably / "I'll assume" answer written into the KB is a FAILURE, not a finding. Turn it into a Q&A entry.
  • Never silently reconcile a contradiction — record both sides and ask which is right.
  • State a fact only when you can ground it from the artifacts with certainty (cite the source). Otherwise, ASK.

The deferral machinery is already built in — use it: the Step 0cx (domain), 0d (doc-set), 0f (path), and Step 5c (term-exclusion) gates are PAUSE-FOR-USER-DECISION points; sub-agents write open questions to .aid/knowledge/.scout-questions.tmp; Step 6b consolidates them into STATE.md ## Q&A (Pending); and the Q-AND-A state resolves them with the user before approval. Every disambiguation flows through this path — none is decided silently.

Read the full file on GitHub · 387 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.

  1. 8d ago First seen · 387 lines · 118 tokens per session scan A db80ab3eef6a

Subscribe to this mod's changes

aid-discover is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed yesterday), licensed MIT. It adds 118 tokens to every session and 5,595 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens