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 eristoddle/agent-skills --skill living-plangit clone --depth 1 https://github.com/eristoddle/agent-skillsWrote 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/eristoddle/agent-skills/living-plan)<a href="https://agentmods.dev/skills/eristoddle/agent-skills/living-plan"><img src="https://agentmods.dev/badge/skills/eristoddle/agent-skills/living-plan/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/eristoddle/agent-skills/living-plan"><img src="https://agentmods.dev/badge/skills/eristoddle/agent-skills/living-plan.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.00279 | $0.02480 |
| Opus 5 | $0.00139 | $0.01240 |
| Sonnet 5 | $0.00056 | $0.00496 |
| Haiku 4.5 | $0.00028 | $0.00248 |
Grade A, and why
living-plan 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 12d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
living-plan
This skill owns the planning-doc workflow: a hot, lean PLAN.md (the every-session
decision record) paired with a TASKS.md handoff contract and an implementer agent, with
cooled material progressively disclosed into a docs/ tree so the hot layer stays
cheap to carry in context.
Five actions, and one is different in kind. grill generates the material: it interviews
the user round-by-round until the design tree has been visited, and writes the result into
the decision record. The other four (scaffold, adopt, rebalance, evict-tasks) only
reshape what already exists. Grill is also the only thing that ever moves an item out of the
cold containers — threads ripen along a ladder (parking lot → open question → decision → task
queue) and nothing else here promotes one. That ladder is the point for the audience this
serves: someone experimenting, who does not know the shape up front and needs a breadcrumb
trail of where the thinking has already been.
The handoff contract treats the active task as a serial queue of numbered pieces — stack
a few (pacing: plan ahead while the agent grinds) or many (unattended: queue work and walk
away). The agent works the queue top-to-bottom, skips a blocked piece rather than halting,
and logs run-state into the task doc on every stop so a killed session is recoverable. (Full
shape in templates/TASKS.template.md + the agent template.)
It is portable across projects and tolerant of naming variance (TASKS.md vs
TASK.md, CLAUDE.md vs AGENTS.md). It does NOT assume this skill's home project.
External task mirrors
Some projects keep a second copy of the task list outside the repo — a note in a notes app, a
shared doc, a tracker — because items get captured when the user is away from the machine.
This skill supports exactly one thing for that case: an optional pointer line in the
conductor, named at scaffold time (or backfilled by adopt), saying where the mirror is and
that it must be reconciled at the start and end of a queue.
What ships with it
12 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.
- references/cooled-heuristic.md 4.8 KB
- references/ledger.md 1.8 KB
- templates/agents/implementer.template.md 2.5 KB
- templates/CLAUDE-blurb.template.md 4.1 KB
- templates/PLAN.template.md 1.6 KB
- templates/QUESTION.template.md 1.2 KB
- templates/TASKS.template.md 2.2 KB
- workflows/adopt.md 3.7 KB
- workflows/evict-tasks.md 4.9 KB
- workflows/grill.md 9.5 KB
- workflows/rebalance.md 3.1 KB
- workflows/scaffold.md 4.5 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.
- 12d ago First seen · 151 lines · 279 tokens per session scan A 29fdb8ff5455
living-plan is a skill published in the GitHub repository eristoddle/agent-skills (2 stars, last pushed 17d ago), licensed MIT. It adds 279 tokens to every session and 2,480 once invoked, about $0.0014 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.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.