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 agentmods add skills/youglin-dev/aha-loop/roadmapnpx skills add YougLin-dev/Aha-Loop --skill roadmapgit clone --depth 1 https://github.com/YougLin-dev/Aha-LoopWhat 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 | $0.00039 | $0.02760 |
| Opus 5 | $0.00019 | $0.01380 |
| Sonnet 5 | $0.00008 | $0.00552 |
| Haiku 4.5 | $0.00004 | $0.00276 |
Grade A, and why
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 2d 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 — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Skill
Plan project execution by creating milestones and organizing PRDs into an executable queue.
Workspace Mode Note
When running in workspace mode, all paths are relative to .aha-loop/ directory:
- Vision analysis:
.aha-loop/project.vision-analysis.md - Architecture:
.aha-loop/project.architecture.md - Roadmap:
.aha-loop/project.roadmap.json - PRD files:
.aha-loop/tasks/
The orchestrator will provide the actual paths in the prompt context.
The Job
- Read
project.vision-analysis.mdandproject.architecture.md - Decompose project into milestones
- Break each milestone into PRDs
- Order PRDs by dependencies
- Output
project.roadmap.json - Generate initial PRD files in
tasks/
Milestone Strategy
Standard Milestone Structure
| Milestone | Focus | Goal |
|---|---|---|
| M0: Foundation | Project scaffolding, CI/CD, tooling | Development environment ready |
| M1: MVP | Core features only | Minimal usable product |
| M2: Essential | Important features | Feature-complete for basic use |
| M3: Enhanced | Nice-to-have features | Polished product |
| M4: Optimization | Performance, UX polish | Production-ready |
Milestone Sizing
Each milestone should:
- Be completable in a reasonable timeframe
- Have 3-7 PRDs (avoid too many or too few)
- Deliver tangible, testable value
- Build on previous milestones
PRD Decomposition
From Features to PRDs
For each milestone, break down features into PRDs:
Milestone: M1 - MVP
├── PRD-001: Project Scaffolding
├── PRD-002: Database Schema
├── PRD-003: Core Data Models
├── PRD-004: Basic API Endpoints
└── PRD-005: Minimal UI
PRD Sizing
Each PRD should:
- Take 1-5 Aha Loop iterations (5-25 stories)
- Focus on one coherent feature area
- Be independently testable
- Not depend on unfinished PRDs
PRD Ordering
Order PRDs by dependencies:
- Infrastructure first - Project setup, database, auth
- Backend before frontend - APIs before UI that uses them
- Core before optional - Must-have before nice-to-have
- Data before presentation - Models before views
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.
- 2d ago First seen · 458 lines · 39 tokens per session scan A bd86d0f49917
roadmap is a skill published in the GitHub repository YougLin-dev/Aha-Loop (181 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 2,760 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.