plan-register

A procedure for registering a plan document for protection. It reads the plan, summarizes its important details, and records it through the collaboration system.

In plain words
What is it for?
Use it after creating a plan or when beginning implementation, giving the plan file path so it can be protected.
Why use it?
It helps prevent an active plan from being accidentally deleted during context compaction or other session changes.

Skill for Claude CodeCodex

Part of the session-collab plugin — 3 skills, 2 commands, 4 hooks, 1 MCP server shipped together

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/leaf76/session-collab-mcp/plan-register
Any agent
npx skills add leaf76/session-collab-mcp --skill plan-register
Clone the repo
git clone --depth 1 https://github.com/leaf76/session-collab-mcp

Made for: Claude Code, Codex.

Or install session-collab, the plugin that ships this one along with the rest of its 3 skills, 2 commands, 4 hooks, 1 MCP server.

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 413 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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00413
Opus 5 $0.00009 $0.00206
Sonnet 5 $0.00003 $0.00083
Haiku 4.5 $0.00002 $0.00041

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

Security

Grade A, and why

plan-register 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.

plugin/skills/plan-register/SKILL.md · 72 lines

What it actually says

Plan Registration

Register a plan document to protect it from accidental deletion during context compaction.

When to Use

  • After creating a new plan document
  • When starting to implement a plan
  • When you want to ensure a document survives context summarization

Required Actions

Step 1: Identify the Plan File

Get the plan file path. If not provided, ask the user.

Step 2: Read the Plan Content

Use Read to get the plan content for summary extraction.

Step 3: Extract Key Information

From the plan content, identify:

  • Title: The plan's main objective
  • Key Steps: Major implementation steps (3-5 bullet points)
  • Dependencies: Any requirements or blockers

Step 4: Register the Plan

Call collab_protect with:

  • action: "register"
  • session_id: Your session ID
  • file_path: Path to the plan file
  • type: "plan"
  • title: Extracted title
  • content_summary: Concise summary (key steps, goals)

Step 5: Confirm Registration

Display the registration result.

Output Format

### Plan Registered

| Item | Value |
|------|-------|
| Title | [plan title] |
| File | [file path] |
| Priority | 95 (high) |
| Pinned | Yes |

### Summary Saved
[Brief summary that will be preserved]

### Protection Active
This plan is now protected from accidental deletion and context-loss mistakes.

Notes

  • Plans are registered with very high priority protection
  • Plans are pinned so they appear in active memory and protected file listings
  • Use collab_protect with action="list" to inspect protected plans and files
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.

  1. 2d ago First seen · 72 lines · 17 tokens per session scan A 5116b7314d86

Subscribe to this mod's changes

plan-register is a skill published in the GitHub repository leaf76/session-collab-mcp (2 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 413 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

xcodebuildmcp-structured-output-review

Use when reviewing XcodeBuildMCP structured output schema changes, schema versioning, manifest outputSchema metadata, and JSON fixture compatibility.

getsentry/XcodeBuildMCP · 37 tokens

onboarding

Use for /onboarding, or when a new member's onboarding is not yet complete — runs the deterministic VERIFY, ORIENT, INVITE, FIRSTHANDOFF welcome flow.

egregore-labs/egregore · 38 tokens

teams-connect

Set up Microsoft Teams as a notification channel for your Egregore — registers an Azure bot, uploads the app, and binds a channel. Use for /teams-connect, 'connect teams', or 'set up teams notifications'.

egregore-labs/egregore · 48 tokens

mcp-transport-contract-auditor

Route shaft-mcp transport-contract audits to the canonical playbook.

ShaftHQ/SHAFT_ENGINE · 22 tokens

cortex-automate

Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to…

cdeust/Cortex · 93 tokens