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 agentmods add skills/backnotprop/plannotator/plannotator-annotatenpx skills add backnotprop/plannotator --skill plannotator-annotategit clone --depth 1 https://github.com/backnotprop/plannotatorWhat 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 | $0.00029 | $0.00171 |
| Opus 5 | $0.00015 | $0.00086 |
| Sonnet 5 | $0.00006 | $0.00034 |
| Haiku 4.5 | $0.00003 | $0.00017 |
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 yesterday.
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 Annotate (Kiro)
Run:
PLANNOTATOR_ORIGIN=kiro-cli plannotator annotate $ARGUMENTS
$ARGUMENTS should be a markdown or plain-text config file path (.md, .txt, .yaml, .json, .toml, .ini, .csv, .log, …), folder path, html file path, or URL.
If the command reports that the arguments could not be resolved to a file, URL, or folder, work out which target the user means and re-run the command yourself with that concrete path or URL.
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.
- yesterday First seen · 18 lines · 29 tokens per session scan A 22029123a304
plannotator-annotate is a skill published in the GitHub repository backnotprop/plannotator (8,256 stars, last pushed 2d ago), licensed Apache-2.0. It adds 29 tokens to every session and 171 once invoked, about $0.0001 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
cache-notes
Fetch & embed AI transcripts as Obsidian callouts. Args: , all, refresh . Prompts for URLs if empty.
recap
Produce a weekly/date-range recap from emails, Slack, Jira/Confluence, and vault notes. Args: [dates]. Default = this week.
fill-participants
Resolve and fill Participants frontmatter + link unlinked names in body. Args: , all.
followup-todos
Extract action items as plain markdown bullets (with confirmation). Args: . No args = run /note-status pending --step=todos.
meeting
Create or wrap meeting notes. Args: {title} [folder=X], wrap , wrap pending [today|this week|dates]. No args = pick from Google Calendar.
note-status
Verify meeting notes are fully processed. Args: , [dates], all, pending [dates] [--step=X]. Shows which wrap steps are complete or missing.