Borrowing it
Nothing to install: this file belongs to YougLin-dev/Aha-Loop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/YougLin-dev/Aha-Loop/main/.agents/skills/plan-review/SKILL.mdgit clone --depth 1 https://github.com/YougLin-dev/Aha-LoopWrote 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/youglin-dev/aha-loop/plan-review)<a href="https://agentmods.dev/skills/youglin-dev/aha-loop/plan-review"><img src="https://agentmods.dev/badge/skills/youglin-dev/aha-loop/plan-review/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/youglin-dev/aha-loop/plan-review"><img src="https://agentmods.dev/badge/skills/youglin-dev/aha-loop/plan-review.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.00040 | $0.01798 |
| Opus 5.5 | $0.00016 | $0.00719 |
| Sonnet 5.5 | $0.00008 | $0.00360 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
plan-review 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 2mo 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Review Skill
Evaluate research findings and decide whether to adjust upcoming stories in the PRD.
The Job
- Read the research report for the current story
- Evaluate if findings impact the current or future stories
- Decide on plan modifications (if any)
- Update
prd.jsonwith changes - Document all changes in
changeLog - Ensure plan remains coherent and achievable
When to Modify the Plan
MODIFY stories when research reveals:
- A better technical approach than originally planned
- Missing prerequisite steps
- Stories that should be split (too large for one context)
- Stories that can be combined (too small, tightly coupled)
- Changed dependencies requiring reordering
- New edge cases requiring additional acceptance criteria
DO NOT modify when:
- The finding is interesting but doesn't affect implementation
- Changes would invalidate already-completed stories
- The modification is scope creep (outside original PRD goals)
Types of Plan Modifications
1. Modify Existing Story
Update acceptance criteria, description, or research topics.
{
"timestamp": "2026-01-29T12:00:00Z",
"storyId": "US-002",
"action": "modified",
"reason": "Research found that existing badge component supports priority colors, simplifying implementation",
"changes": {
"acceptanceCriteria": {
"removed": ["Create new PriorityBadge component"],
"added": ["Reuse Badge component with priority color variant"]
}
}
}
2. Add New Story
Insert a prerequisite or follow-up story.
{
"timestamp": "2026-01-29T12:00:00Z",
"storyId": "US-001.5",
"action": "added",
"reason": "Research revealed need for database index on priority column for filter performance",
"insertAfter": "US-001"
}
3. Split Story
Break a story into smaller pieces.
{
"timestamp": "2026-01-29T12:00:00Z",
"storyId": "US-003",
"action": "split",
"reason": "Story too large - separating dropdown component from save logic",
"splitInto": ["US-003a", "US-003b"]
}
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.
- 2mo ago First seen · 299 lines · 40 tokens per session scan A ba332c33449e
plan-review is a skill published in the GitHub repository YougLin-dev/Aha-Loop (178 stars, last pushed 9mo ago), licensed MIT. It adds 40 tokens to every session and 1,798 once invoked, about $0.0002 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-30.
plan-review compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| plan-reviewYougLin-dev/Aha-Loop | Skill | 178 | 9mo ago | MIT | A | 40 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 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 |