Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add paulbaranowski/wild-horses/plugin install plan-keeperWrote 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/paulbaranowski/wild-horses/plan-list)<a href="https://agentmods.dev/skills/paulbaranowski/wild-horses/plan-list"><img src="https://agentmods.dev/badge/skills/paulbaranowski/wild-horses/plan-list/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/paulbaranowski/wild-horses/plan-list"><img src="https://agentmods.dev/badge/skills/paulbaranowski/wild-horses/plan-list.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.00056 | $0.01921 |
| Opus 5 | $0.00028 | $0.00960 |
| Sonnet 5 | $0.00011 | $0.00384 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
plan-list 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 10d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-list
List the saved plans in ~/plans/<repo>/, newest-first, grouped by Status. This is the read-only member of the plan-keeper family: it shows what's there and stops. It never reads a plan body, never changes Status, and never moves or deletes a file. To pick a plan up and route it into the pipeline, that's plan-do; to manage the cross-repo groundcrew queue, that's plan-crew.
The bundled plan_keeper_cli.py does all the work (repo derivation, newest-first sort, status grouping, empty-state detection); this skill just invokes it and presents the result.
Quick reference
- Reads: every
~/plans/<repo>/*.mdwith frontmatter (one level deep;done/,deferred/are separate states). - Writes: nothing. No confirmation gate — there's nothing to confirm.
<repo>: auto-derived from the current repo, or an explicit override — see ../../repo-derivation.md.- Default view: active plans (
in-progress,in-review,todo,backlog), grouped in that order, newest-first within each group. - Other states:
--state doneand--state deferredlist the archived / shelved plans on request. - Grouped view:
list --groupclusters a project's stages (shared slug) together, each labelled by its Kind and ordered along theidea → exec-planpipeline. Use it when the user wants to see how one project's plans relate. Mutually exclusive with--status. - Sibling boundary:
plan-listonly shows. The moment the user wants to act on a plan — start it, queue it, edit frontmatter, archive it — hand off toplan-do/plan-crew/plan-update/plan-done.
Procedure
1. Determine the repo
Check the user's invocation for an explicit override. Recognize:
- "list plans in
<name>" - "plan-list
<name>" - "show plans for/from
<name>" - "what plans are in the
<name>folder/bucket"
If present, normalize it per ../../repo-derivation.md and pass it as --override <name>. Otherwise the CLI auto-derives from the current directory — no flag needed.
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.
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.
- 10d ago First seen · 118 lines · 56 tokens per session scan A 8b7a93147f8d
plan-list is a skill published in the GitHub repository paulbaranowski/wild-horses (12 stars, last pushed 22d ago), licensed MIT. It adds 56 tokens to every session and 1,921 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…