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 plannotator-lastgit 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-last)<a href="https://agentmods.dev/skills/backnotprop/plannotator/plannotator-last"><img src="https://agentmods.dev/badge/skills/backnotprop/plannotator/plannotator-last/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-last"><img src="https://agentmods.dev/badge/skills/backnotprop/plannotator/plannotator-last.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
- Socket warn
- Snyk 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.00027 | $0.00285 |
| Opus 5.5 | $0.00011 | $0.00114 |
| Sonnet 5.5 | $0.00005 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
plannotator-last 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 10d 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.
What it actually says
Plannotator Last
Message annotations
!plannotator annotate-last $ARGUMENTS
Your task
The output above will be one of:
- The exact text
The user approved., an "Approved with Notes" message, OR a JSON object with"decision": "approved". The user approved your last message. If it is the Approved with Notes message, or that object also carries a"feedback"field, the user approved with notes: read them and carry them into subsequent work — they are non-blocking guidance, not a request to revise the message. Otherwise acknowledge with a single sentence ("Approved.") and stop. Either way, do not begin any work. - Empty, OR a JSON object with
"decision": "dismissed". The user closed the session without requesting changes. Acknowledge with a single sentence ("Annotation session closed.") and stop. Do not begin any work. - Plaintext annotation feedback, OR a JSON object with
"decision": "annotated"and a"feedback"field. Address the feedback. The user has reviewed your last message and provided specific annotations and comments.
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.
- 10d ago Changed 1a979daa6b39
- 1mo ago First seen · 21 lines · 27 tokens per session scan A bbcd69c3d424
plannotator-last is a skill published in the GitHub repository backnotprop/plannotator (9,469 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 285 once invoked, about $0.0001 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.
Other skills, from other repositories
mykg
Universal Knowledge Graph for accumulating and organizing knowledge from any source. Use when ingesting documents, answering questions, maintaining wiki pages, or working with project-specific knowledge bases.
project-skill
Project-specific instructions for this workspace. Use when ingesting sources and maintaining wiki for this domain.
mykg
../../SKILL.md.
ralplan
Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution.
remember
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs.
southwest
Search Southwest Airlines fares and points pricing via Patchright browser automation. SW is not in any GDS or API. Covers all fare classes, Companion Pass value, and fare drop monitoring.