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 ndom91/open-plan-annotator --skill plan-review-triggersgit clone --depth 1 https://github.com/ndom91/open-plan-annotatorWrote 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/ndom91/open-plan-annotator/plan-review-triggers)<a href="https://agentmods.dev/skills/ndom91/open-plan-annotator/plan-review-triggers"><img src="https://agentmods.dev/badge/skills/ndom91/open-plan-annotator/plan-review-triggers.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00199 | $0.01243 |
| Opus 5 | $0.00100 | $0.00622 |
| Sonnet 5 | $0.00040 | $0.00249 |
| Haiku 4.5 | $0.00020 | $0.00124 |
Grade A, and why
plan-review-triggers 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Review Triggers
This plugin (open-plan-annotator) installs a hook on ExitPlanMode that opens a browser UI where the user marks up plans directly — deletions, replacements, insertions, comments — and returns structured feedback. Inline markdown plans bypass that workflow.
Hard Rule: Annotator Required When Triggers Match
Inline plans are a bug. When any trigger below fires, route through the annotator:
- Assistant-initiated (you decided a plan is needed): call
EnterPlanMode, draft, thenExitPlanMode— fires the annotator hook. - User-initiated ("draft a plan", "/plan", etc.): invoke
/annotate-plan <task>.
Mechanical Heuristic
Annotator REQUIRED when the response would contain ANY of:
- 3 or more file paths to create or modify
- 2 or more option/tradeoff comparisons for the user to choose between
- A
Plan:,Steps:,Concrete changes:,Implementation:,Approach:section header - A numbered/bulleted list of action items the user is expected to react to
- A multi-section proposal with decision points
Hard gate. Count file paths. Count options. If the count crosses the line, the inline response is not allowed.
Task Shape Triggers
- Creating or modifying more than 2 files
- Architectural or structural changes
- Refactoring, migration, or feature additions
- Bug fixes that require investigation
- Anything the user has not explicitly described step-by-step
Phrase Triggers
- User says "draft a plan", "let's plan X", "what's the approach", "give me options", "how should we tackle this", "what would it look like"
- Response would contain "recommended approach", "implementation plan", "proposed fix", "rollout plan", "here's what I'd do", "concrete file changes"
- Any moment you'd ask "want me to proceed?" / "shall I draft this?" / "OK to proceed?" / "sound good?"
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.
- 8d ago First seen · 101 lines · 199 tokens per session scan A ebac34b76bea
plan-review-triggers is a skill published in the GitHub repository ndom91/open-plan-annotator (93 stars, last pushed 6d ago), licensed MIT. It adds 199 tokens to every session and 1,243 once invoked, about $0.0010 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
openai-docs
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, latest/current/default-model prompting guidance, or model upgrade and prompt-upgrade guidance; use…
Presentations
Read, create or edit PowerPoint or Google Slides decks. Use for presentation, slide deck, PowerPoint, PPT, PPTX, or Google Slides requests.
work
Execute spec.json (plan mode) or review.findings.json (fix-findings mode) by dispatching subagents per chunk. Triggers on "work on", "implement", "execute plan", "carry on", "continue".
omd-path
A decision map for breaking a large or unclear software project into smaller questions and decisions. It can store the map in Markdown files or, when configured, in GitHub Issues and sub-issues.
omd-review
A structured review of code changes that looks for correctness, security, missing requirements, and edge cases. It can review everything changed in the current branch or a selected part of the codebase.
django-tdd
Test-driven development patterns for Django covering pytest, Django TestCase, factoryboy, test client, and best practices for testing Django applications.