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-update-roadmapgit 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-update-roadmap)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-update-roadmap"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-roadmap/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-update-roadmap"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-roadmap.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.00155 | $0.02008 |
| Opus 5 | $0.00077 | $0.01004 |
| Sonnet 5 | $0.00031 | $0.00402 |
| Haiku 4.5 | $0.00015 | $0.00201 |
Grade A, and why
aid-update-roadmap 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 9d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Roadmap (revise direction entries outside ## MVP)
/aid-update-roadmap revises the direction entries of .aid/knowledge/roadmap.md
outside the ## MVP section. It is an update-stage skill under the shared contract in
.claude/aid/templates/design-lifecycle.md (class 1), reading and consuming a seed
from .aid/design/roadmap.md when one is present, and never requiring one.
- Boundary vs
/aid-update-mvp: this skill owns every byte ofroadmap.mdexcept the## MVPsection. It never creates, edits, or removes## MVPcontent. The- [MVP](#mvp)index entry in## Contentsis left in place whether or not the section exists -- the index is outside the## MVPbyte range and belongs to this skill's region. - Destination absent: when
roadmap.mddoes not exist this skill routes to/aid-create-roadmap, names it explicitly, and writes nothing. - Not a numbered pipeline phase; does not route to
/aid-execute.
State machine: INTAKE -> GUARD -> UPDATE -> VERIFY -> PRESENT -> DONE.
Print the [State: NAME] -- {purpose} entry line on each state.
State: INTAKE
- Require a subject. Empty argument -> ask one bootstrapping question ("What would you like to revise in the roadmap -- entries to add, update, supersede, or move between horizons?") and wait.
- Allocate, exactly per
design-lifecycle.md § Skill shape -- Allocation-- the Work Initiation Gate, theninitiator: aid-update-roadmap,active_skill: aid-update-roadmap,pipeline.path: lite,lifecycle: Running.phaseis not driven. - Read the destination at
.aid/knowledge/roadmap.md. If absent, route to/aid-create-roadmap-- name it explicitly in the response -- and write nothing. Setlifecycle: Paused-Awaiting-Input. Advance to DONE without proceeding further. - Read the seed at
.aid/design/roadmap.mdif one exists. Note its presence or absence; do not require it. - Ask the derived-outputs question -- every run, unconditionally: "Which previously created outputs should be updated alongside roadmap.md?" Wait for the user's answer before proceeding. Write no stored list and no tracking metadata anywhere.
- Classify complexity (model + effort) for the
aid-architectdispatch below; verifier tier >= producer tier (agent-dispatch-tiering.md).
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.
- 9d ago First seen · 168 lines · 155 tokens per session scan A cc48acf9dd50
aid-update-roadmap is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 2d ago), licensed MIT. It adds 155 tokens to every session and 2,008 once invoked, about $0.0008 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…
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…
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…