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-askgit 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-ask)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-ask"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-ask/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-ask"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-ask.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 74 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 124 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00151 | $0.02590 |
| Opus 5.5 | $0.00060 | $0.01036 |
| Sonnet 5.5 | $0.00030 | $0.00518 |
| Haiku 4.5 | $0.00015 | $0.00259 |
Grade A, and why
aid-ask 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 25d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Q&A
Answers a free-form question about the project in one pass. Reads context from the Knowledge Base, the live codebase, and in-flight AID work state, then replies with source citations.
Write scope (gap-capture only). /aid-ask writes to exactly one place
and only when the context is insufficient to answer: it appends a ### Q{N}
Query-Gap entry to a ## Q&A (Pending) section of a STATE.md backlog file.
No KB doc, settings file, or code file is ever written. The answer path stays
fully read-only; only the gap-append branch writes (NFR-6/C4: capture-and-flag,
never auto-apply).
Not a numbered pipeline phase. /aid-ask is an optional, on-demand skill
outside the Discover-Execute flow. No work folder, no STATE.md of its own.
Single-shot, no state machine. One pass: read context -> answer -> exit.
Pre-flight
- Confirm a question was supplied. If
/aid-askis invoked with no argument, print:
Then exit without answering.Usage: /aid-ask <question> Example: /aid-ask "Which agent tier handles code review?"
Execution: answer the question
Step 1 — Classify the question
Decide whether the question is trivial or broad/expensive:
- Trivial: answerable by reading a small number of known KB docs or a specific file path. Examples: "What does aid-housekeep do?", "Where does the generator output go?", "What is the allowed-tools list for aid-researcher?"
- Broad/expensive: requires deep codebase traversal, cross-file pattern matching, or analysis of many files. Examples: "What are all the places where STATE.md is written?", "Summarize every Q&A in the current discovery cycle", "How does the render pipeline handle tool-name remapping across all profiles?"
Step 2a — Trivial question: answer inline
Read only the files needed to answer:
- Load
.aid/knowledge/INDEX.mdto identify which KB docs are relevant. - Read the relevant KB docs (e.g.,
architecture.md,coding-standards.md,module-map.md,pipeline-contracts.md,schemas.md, etc.) usingRead. - Glob or Grep specific files as needed (e.g., locate a SKILL.md or AGENT.md, check a script header, read a work STATE.md).
- Compose the answer with inline citations:
- KB doc: cite as "
architecture.md§Section" orcoding-standards.md §7b. - File path: cite as
.agents/skills/aid-ask/SKILL.md. - Work state: cite as
work-001-kb-skills STATE.mdorwork-NNN STATE.md §Section.
- KB doc: cite as "
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.
- 25d ago Changed eff527d82e52
- 2mo ago First seen · 247 lines · 151 tokens per session scan A 8d35de7f9ac9
aid-ask is a skill published in the GitHub repository AndreVianna/aid-methodology (6 stars, last pushed 10d ago), licensed MIT. It adds 151 tokens to every session and 2,590 once invoked, about $0.0006 per session on Opus 5.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.
aid-ask compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| aid-askAndreVianna/aid-methodology | Skill | 6 | 10d ago | MIT | A | 151 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |