planner

planner is an agent for coding agents from vosslab/vosslab-skills. It costs 20 tokens per session (218 once invoked), scanned A, original, MIT.

An agent that writes planning documents, architecture notes, and implementation plans without changing production code, tests, or runtime settings.

In plain words
What is it for?
Use it to create documentation under docs or plan files, assess system stability, propose architecture changes, and plan narrowly scoped fixes or experiments.
Why use it?
It keeps planning separate from implementation and directs unstable projects toward focused stabilization work before larger redesigns.

Agent

Part of the vosslab-skills plugin — 42 skills, 14 agents 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 agents/vosslab/vosslab-skills/planner
Clone the repo
git clone --depth 1 https://github.com/vosslab/vosslab-skills

Or install vosslab-skills, the plugin that ships this one along with the rest of its 42 skills, 14 agents.

Wrote 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.

agentmods badge for planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/vosslab/vosslab-skills/planner.svg)](https://agentmods.dev/agents/vosslab/vosslab-skills/planner)
Your own site
<a href="https://agentmods.dev/agents/vosslab/vosslab-skills/planner"><img src="https://agentmods.dev/badge/agents/vosslab/vosslab-skills/planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 218 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.00020 $0.00218
Opus 5 $0.00010 $0.00109
Sonnet 5 $0.00004 $0.00044
Haiku 4.5 $0.00002 $0.00022

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

Security

Grade A, and why

planner 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.

agents/planner.md · 22 lines

What it actually says

Create and update planning documents, architecture docs, and implementation plans. Write only documentation artifacts under docs/ or plan files. Never write or modify production code, test files, or runtime configuration.

Assess system stability before proposing architecture changes. If the system has unresolved failures, produce a stabilization plan (narrow fixes, experiment log) instead of a refactor plan. Never mix root-cause debugging, algorithm redesign, and organizational program management in one document. Each plan addresses exactly one abstraction level. If stabilization experiments show the algorithm itself is wrong (not just the code), recommend scrapping the approach and designing a new algorithm before resuming.

Escalation paths:

  • Cross-cutting design change -> architect (approval or rejection)
  • Architecture decision -> architect (approval required)
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 · 20 tokens per session scan A d26611f80240

Subscribe to this mod's changes

planner is an agent published in the GitHub repository vosslab/vosslab-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 20 tokens to every session and 218 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-31.