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 petekp/claude-code-setup --skill vignette-todo-rungit clone --depth 1 https://github.com/petekp/claude-code-setupWrote 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/petekp/claude-code-setup/vignette-todo-run)<a href="https://agentmods.dev/skills/petekp/claude-code-setup/vignette-todo-run"><img src="https://agentmods.dev/badge/skills/petekp/claude-code-setup/vignette-todo-run/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/petekp/claude-code-setup/vignette-todo-run"><img src="https://agentmods.dev/badge/skills/petekp/claude-code-setup/vignette-todo-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00141 | $0.01698 |
| Opus 5.5 | $0.00056 | $0.00679 |
| Sonnet 5.5 | $0.00028 | $0.00340 |
| Haiku 4.5 | $0.00014 | $0.00170 |
Grade A, and why
vignette-todo-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 23d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vignette TODO run
One run takes a base branch and a list of items from docs/TODOS.md, and ends with one
integration branch Pete tests by hand, a run report under docs/, and the items marked landed.
Read AGENTS.md in the Vignette checkout before planning: the loop, the rules for several
builds on one Mac, and the measuring paragraphs are what the templates enforce.
Roles. The orchestrator (you) plans, briefs, orchestrates, and reviews, and writes no product
code. Delegated agents do the code and the verification, one worktree each. One integrator, one
adversarial reviewer, and, when asked, one architecture sweep. launchers/claude.md says how
to spawn them in Claude Code; in Codex use its own delegation with the same prompts.
Inputs to settle before anything is spawned: the base branch (foundation unless said), the run
tag (todoN, one more than the last todoN/* branch in git branch -a), the items in Pete's
words, and whether Pete is at the Mac (the templates assume he may be).
1. Plan, and show it
Group the items by the files they touch so agents do not collide. Read the items, grep for the
files each names, and check for a shared file between groups (Settings.swift and
DebugPanel.swift are shared by any item that adds a tweak; AGENTS.md and README.md by
every item). Inside a group, order items so a measurement comes before the change that would
confound it. Show Pete the grouping (a table: agent, branch, items, files), the order inside
each group, the shared files, and the merge order. Wait for a yes unless he said to proceed.
2. Set up
scripts/setup-run.sh <run> <base> <name>... creates, for each agent name, the worktree
~/Code/vignette-todo/<name> on <run>/<name> from <base>, copies scripts/signing.env, runs
pnpm install in web/, and makes ~/Code/vignette-todo/<name>-scratch with shots/,
captures/, and a settings.json seeded from ~/.config/vignette/settings.json with jq
(screenshotsFolder = the shots folder, syncAppleSaveLocation false, debug true,
launchAtLogin false, copyOnCapture false, annotateOnCapture false). It archives a previous
run's briefs, reports, and scratch folders into ~/Code/vignette-todo/<previous run>-archive/
first. It prints the settings mtime; record it.
What ships with it
10 files 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.
- agents/openai.yaml 283 B
- launchers/claude.md 1.6 KB
- references/bootstrap-prompt-2026-09-17.md 7.3 KB
- scripts/finish-run.sh 2.4 KB runs code
- scripts/setup-run.sh 2.4 KB runs code
- templates/ARCHITECTURE.md 4.1 KB
- templates/BRIEF.md 11 KB
- templates/INTEGRATOR.md 3.5 KB
- templates/ITEM-example.md 5.3 KB
- templates/REVIEWER.md 2.0 KB
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.
- 23d ago First seen · 93 lines · 141 tokens per session scan A a5cf8be1adb1
vignette-todo-run is a skill published in the GitHub repository petekp/claude-code-setup (48 stars, last pushed 10d ago), licensed MIT. It adds 141 tokens to every session and 1,698 once invoked, about $0.0006 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-09-23.
Other skills, from other repositories
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
github-monitor
Watch your GitHub repos across four views - a combined urgency monitor (stale PRs, new issues, releases), a new-issue triage queue, a release upgrade digest, or your own opened-PR tracker.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.