A runner for continuing a saved personal protocol, meaning a set of repeated steps stored in files. It reads the protocol and its progress log to choose the next unfinished action.

Use it to continue a routine, record progress, review what has been done, or apply the protocol’s own adaptation rules.

It keeps ongoing routines consistent across sessions instead of relying on memory or starting over.

vana-run — Skill by vanadotso

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/vanadotso/agent-plugin/vana-run

Any agent

npx skills add vanadotso/agent-plugin --skill vana-run

Clone the repo

git clone --depth 1 https://github.com/vanadotso/agent-plugin

Made for: Claude Code, Codex.

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 575 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.

Model	Per session	Once invoked
Fable 5	$0.00030	$0.00575
Opus 5	$0.00015	$0.00287
Sonnet 5	$0.00006	$0.00115
Haiku 4.5	$0.00003	$0.00057

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

Security

Grade A, and why

vana-run 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 2d 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.

skills/vana-run/SKILL.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Protocol runner

Protocols persist as files in the user's Data:

protocols/<slug>/protocol.md          one protocol: seven H1 sections
protocols/<slug>/log/<YYYY-MM-DD>.md  one file per day, time-headed entries

The user's Data is behind the Vana MCP server. Read a protocol or log with its read_file tool, save with write_file, and list or search with run_command.

The saved protocol is the source of truth. Read it before you choose the next action, record progress, or review progress. Use the protocol's own steps, names, units, adaptations, and review rules.

When the user names a protocol loosely, list protocols/ and match the slug. If more than one protocol matches, ask which one they mean.

A run is the work completed while following a protocol. Its log records enough state to determine progress and the next action.

Continue a protocol

Read protocol.md and the most recent log entries.
Find the next unfinished action from # Protocol and the recorded progress.
Apply a relevant rule from # Adaptation when the user's context calls for one. Name the rule you applied.
Give the user the complete next action with every detail the protocol specifies.

This branch is complete when the user can act without opening the saved file.

Record progress

Read Log format.
Take the fields and units from # Tracking & Review. Ask a question only when a missing value would change the saved entry or the next action.
Add the entry to protocols/<slug>/log/<YYYY-MM-DD>.md for the date when the work happened. Read an existing file first because write_file replaces the whole file.
Confirm what you saved in one line.

This branch is complete when the log preserves the user's report in the shape defined by the protocol.

Review progress

Read the log span the review covers.
Compare the entries with the goal and review rules in # Tracking & Review.
State what is complete, what remains, and any pattern supported by the entries.
End with the next action. When the protocol defines review choices, use one of those choices and cite the log entries that support it.

Read the full file on GitHub · 53 lines

Files

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.

references/log-format.md 1.1 KB

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.

2d ago First seen · 53 lines · 30 tokens per session scan A 8ba12f650e62

Subscribe to this mod's changes

vana-run is a skill published in the GitHub repository vanadotso/agent-plugin (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 30 tokens to every session and 575 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.

Planning Productivity

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens