Borrowing it
Nothing to install: this file belongs to ComputerSaysNull/claude-delegate-local-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ComputerSaysNull/claude-delegate-local-mcp/main/.claude/skills/session-plan/SKILL.mdgit clone --depth 1 https://github.com/ComputerSaysNull/claude-delegate-local-mcpWrote 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/computersaysnull/claude-delegate-local-mcp/session-plan)<a href="https://agentmods.dev/skills/computersaysnull/claude-delegate-local-mcp/session-plan"><img src="https://agentmods.dev/badge/skills/computersaysnull/claude-delegate-local-mcp/session-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/computersaysnull/claude-delegate-local-mcp/session-plan"><img src="https://agentmods.dev/badge/skills/computersaysnull/claude-delegate-local-mcp/session-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.00059 | $0.01130 |
| Opus 5 | $0.00030 | $0.00565 |
| Sonnet 5 | $0.00012 | $0.00226 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
session-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 yesterday.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session plan
Six steps. Step 4 is not optional and step 6 is where you stop.
1. Read. Do not edit.
PLAN.md is the contract. STATUS.md was retired — it does not exist, do not look for
it. For why an item exists: DECISIONS.md. For what shipped and why: CHANGELOG.md. For
what was measured recently: the last few JOURNAL.md entries.
Delegate the reading. delegate_readonly with those documents in files[], one question
per call — a call with no files[] is the dearest shape, not the cheapest. Do not read
them in the main conversation to answer what a delegation could answer. If
delegate_readonly is not available, use the Explore agent.
2. Rank
🔄 outranks everything: finish before starting. Then rank the ⬜ items under Open by
blocking impact ÷ effort. ✅, ❌ and Deferred are out of scope for the ranking.
- An item resting on a claim nobody has measured is a spike, not an item. Rank the spike first, and say what would be run to settle it.
- Check the milestone exit condition the items sit under. An item that does not move that condition is not this session's work, however cheap it looks.
- The exit condition orders the session; it does not size it. Ranking stops when the items run out, not when the first one is picked. A plan holding one item is right only if that item is genuinely a session's worth — say how long you think it is, and if the answer is "half a session", keep ranking.
3. Propose ONE plan
One plan, not a menu. Per item, name:
- the branch (
feat/,fix/,docs/) and the commits it splits into; - the test, and how that test fails without the fix. A check that cannot fail is worse than no check. Say what the negative control is before writing either;
- the owning document —
python scripts/docs_gate.py --owner <path>, never from memory; - the CHANGELOG entry's why: symptom, cause, fix;
- that it is a whole item. If what you are proposing is a fragment of a PLAN entry — a precondition you measured out of it, a first half — say so, and plan the rest of the entry too.
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.
- yesterday First seen · 87 lines · 59 tokens per session scan A ce8bcdf33131
session-plan is a skill published in the GitHub repository ComputerSaysNull/claude-delegate-local-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,130 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-09-11.
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.