plannotator-annotate

A skill that opens Plannotator's annotation interface for a Markdown file, converted webpage, URL, or folder. Plannotator is a browser tool for leaving comments or approval decisions.

In plain words
What is it for?
It is for submitting a file or page for annotation, then handling approval, dismissal, or written feedback.
Why use it?
It collects focused feedback on content or converted pages and tells the agent whether to stop or make changes.

Skill for Claude CodeCodex

Part of the agents plugin — 16 skills, 20 agents, 5 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/wyattowalsh/agents/plannotator-annotate
Any agent
npx skills add wyattowalsh/agents --skill plannotator-annotate
Clone the repo
git clone --depth 1 https://github.com/wyattowalsh/agents

Made for: Claude Code, Codex.

Or install agents, the plugin that ships this one along with the rest of its 16 skills, 20 agents, 5 hooks.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 211 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00211
Opus 5 $0.00017 $0.00105
Sonnet 5 $0.00007 $0.00042
Haiku 4.5 $0.00003 $0.00021

Measured 3d ago against content hash 1ce0bb9efa13, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plannotator-annotate 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 3d 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.

.grok/skills/plannotator-annotate/SKILL.md · 22 lines

What it actually says

Plannotator Annotate

Run:

plannotator annotate $ARGUMENTS

The output will be one of:

  1. The exact text The user approved., or a JSON object with "decision": "approved". Acknowledge with a single sentence and stop. Do not begin any work.
  2. Empty, or a JSON object with "decision": "dismissed". Acknowledge with a single sentence and stop. Do not begin any work.
  3. Plaintext annotation feedback, or a JSON object with "decision": "annotated" and a "feedback" field. Address the feedback in the same conversation.

Do not ask the user to copy shell commands into chat. Run the command yourself.

Changes

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.

  1. 3d ago First seen · 22 lines · 35 tokens per session scan A 1ce0bb9efa13

Subscribe to this mod's changes

plannotator-annotate is a skill published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 12d ago), licensed MIT. It adds 35 tokens to every session and 211 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-31.

Related

Other skills, from other repositories

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include…

vercel-labs/agent-browser · 112 tokens

use-agent-browser-for-airi

Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…

moeru-ai/airi · 87 tokens

opencli-sitemap-author

Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.

jackwener/OpenCLI · 67 tokens

playwright

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.

XiaomiMiMo/MiMo-Code · 45 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

the-open-agent/openagent · 17 tokens