Plannotator is a local browser-based review tool for coding agents that lets people annotate plans, documents, HTML artifacts, code diffs, and pull requests, then send feedback back to the agent. It is used by developers and teams reviewing work from agents across supported coding tools and version-control systems.
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 backnotprop/plannotator --skill plannotatorgit clone --depth 1 https://github.com/backnotprop/plannotatorWrote 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/backnotprop/plannotator/plannotator)<a href="https://agentmods.dev/skills/backnotprop/plannotator/plannotator"><img src="https://agentmods.dev/badge/skills/backnotprop/plannotator/plannotator/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/backnotprop/plannotator/plannotator"><img src="https://agentmods.dev/badge/skills/backnotprop/plannotator/plannotator.svg" alt="Reviewed on agentmods" width="80" 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.00138 | $0.06193 |
| Opus 5.5 | $0.00055 | $0.02477 |
| Sonnet 5.5 | $0.00028 | $0.01239 |
| Haiku 4.5 | $0.00014 | $0.00619 |
Grade B, and why
plannotator scanned grade B with 1 finding 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 today.
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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
Check your tools before you run any command below. If you have a tool named `plannotator` (it can be listed with a prefix, for example `mcp__plannotator__plannotator` in Claude Code, and can need to be loaded through too How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plannotator CLI Reference
Plannotator is a local, browser-based review layer for agent workflows: it opens plans, diffs, and documents in an annotation UI, the human marks them up, and the structured feedback comes back to you on stdout. It installs as a single plannotator binary plus per-host hooks, so plan review fires automatically when you exit plan mode; every other surface is launched explicitly, with the plannotator tool when you have one and with the CLI otherwise. A session runs on a random localhost port (fixed port 19432 in remote mode) and blocks until the reviewer submits feedback, approves, or closes the tab.
This skill is the knowledge layer. The plannotator-review, plannotator-annotate, and plannotator-last skills are thin launchers for the three most common actions; use this reference when you need to pick the right command or flags yourself.
If you have a plannotator tool, always use it
Check your tools before you run any command below. If you have a tool named plannotator (it can be listed with a prefix, for example mcp__plannotator__plannotator in Claude Code, and can need to be loaded through tool search before you call it), always call it instead of running plannotator annotate, plannotator review, or plannotator last. This includes approvals: call it with { "action": "annotate", "target": "<file>", "gate": true }, not --gate --json.
The tool returns at once. End your turn after you call it and wait: the reviewer's decision arrives later as a message. Do not also run the CLI, poll, or reopen the session.
Use the CLI only when you have no such tool, or for what the tool does not do: archive, guide, sessions, review flags other than --base, annotate flags other than --gate and --markdown, and strict gates that a script checks by exit code (--require-approval, --result-file).
Choose the command
| The user wants | Run (CLI, when you have no plannotator tool) |
|---|---|
| Review a plan you produced | Nothing. Plan review opens automatically on plan exit via hooks. Never run bare plannotator yourself. |
| Review and explicitly approve a plan/spec saved as a file | plannotator annotate <file> --gate --json |
| Review current code changes | plannotator review |
| Review a GitHub PR, GitLab MR or Bitbucket Cloud PR | plannotator review <PR_URL> |
| Annotate a markdown, text, config, or HTML file | plannotator annotate <file> |
| Annotate a web page | plannotator annotate <https-url> |
| Annotate a running local app (dev server) | plannotator annotate <http://localhost:PORT/> |
| Pick a file to annotate from a folder | plannotator annotate <folder/> |
| Annotate your latest assistant message | plannotator last |
| Browse past plan decisions | plannotator archive |
| Export or share a Guided Review | plannotator guide export / plannotator guide share |
| Reopen or list live sessions | plannotator sessions |
| Ask the person something they can answer later, without blocking | The plannotator_inbox tool when you have it, else the Inbox's MCP server (plannotator inbox mcp) |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed cd8546bf9bbf
- 3d ago Changed · -6 lines · +33 tokens per session 5b1e1116ecf6
- 4d ago Changed · +2 lines 82a4a7cceaf6
- 5d ago Changed · +10 lines c8de2ae28db5
- 8d ago Changed · +17 lines · +18 tokens per session 2e066271eedc
- 9d ago Changed b519b27477be
- 10d ago Changed · +1 lines 76e5209818e6
- 11d ago Changed · +7 lines · +14 tokens per session scan A → B 73db5a0739f8
- 12d ago Changed · +2 lines abd29b449a82
- 14d ago First seen · 226 lines · 73 tokens per session scan A 564ec7d95c3e
plannotator is a skill published in the GitHub repository backnotprop/plannotator (9,452 stars, last pushed today), licensed Apache-2.0. It adds 138 tokens to every session and 6,193 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
archify-review
Review Archify issues, PRs, or code through value, cost, and impact to support evidence-based maintenance decisions. Use for issue triage, change reviews, and code quality assessments.
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
tech-debt-audit
Thorough, file-cited technical debt audit across 9 dimensions using AST-grep (tree-sitter), grep, LSP, and language-native tooling. Produces TECHDEBTAUDIT.md with severity, effort estimates, and prioritized fixes. Use when asked for codebase health check, tech debt audit, architecture review, code quality assessment…