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 agentmods add skills/kdcokenny/ocx/plan-protocolnpx skills add kdcokenny/ocx --skill plan-protocolgit clone --depth 1 https://github.com/kdcokenny/ocxWhat 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 | $0.00014 | $0.01776 |
| Opus 5 | $0.00007 | $0.00888 |
| Sonnet 5 | $0.00003 | $0.00355 |
| Haiku 4.5 | $0.00001 | $0.00178 |
Grade A, and why
plan-protocol 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 3d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Protocol
Load this skill when creating or updating implementation plans.
TL;DR Checklist
When creating or updating a plan, ensure:
- YAML frontmatter with
status,phase,updated -
## Goalsection (one sentence) -
## Context & Decisionstable with citations (ref:delegation-id) - Phases with status markers:
[COMPLETE],[IN PROGRESS],[PENDING] - Tasks with hierarchical numbering (1.1, 1.2, 2.1)
- Only ONE task marked
← CURRENT - Citations for all research-based decisions
When to Use
- Starting a multi-step implementation
- After receiving a complex user request
- When tracking progress across phases
- After research that informs architectural decisions
When NOT to Use
- Simple one-off tasks → use built-in todos instead
- Pure research/exploration → use delegations only
- Quick fixes that don't need tracking
- Single-file changes with no dependencies
Plan Format
Use plan_save with this exact markdown format:
---
status: STATUS
phase: PHASE_NUMBER
updated: YYYY-MM-DD
---
# Implementation Plan
## Goal
ONE_SENTENCE_DESCRIBING_OUTCOME
## Context & Decisions
| Decision | Rationale | Source |
|----------|-----------|--------|
| CHOICE | WHY | `ref:DELEGATION_ID` |
## Phase 1: NAME [STATUS_MARKER]
- [x] 1.1 Completed task
- [x] 1.2 Another completed task → `ref:DELEGATION_ID`
## Phase 2: NAME [IN PROGRESS]
- [x] 2.1 Completed task
- [ ] **2.2 Current task** ← CURRENT
- [ ] 2.3 Pending task
## Phase 3: NAME [PENDING]
- [ ] 3.1 Future task
- [ ] 3.2 Another future task
## Notes
- YYYY-MM-DD: Observation or decision `ref:DELEGATION_ID`
Frontmatter Fields
| Field | Values | Description |
|---|---|---|
status |
not-started, in-progress, complete, blocked |
Overall plan status |
phase |
Number (1, 2, 3...) | Current phase number |
updated |
YYYY-MM-DD |
Last update date |
Phase Status Markers
| Marker | Meaning |
|---|---|
[PENDING] |
Not yet started |
[IN PROGRESS] |
Currently being worked on |
[COMPLETE] |
Finished successfully |
[BLOCKED] |
Waiting on dependencies |
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.
- 3d ago First seen · 260 lines · 14 tokens per session scan A 3e2708c8c62e
plan-protocol is a skill published in the GitHub repository kdcokenny/ocx (934 stars, last pushed 14d ago), licensed MIT. It adds 14 tokens to every session and 1,776 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-30.
Other skills, from other repositories
ce:plan
Create structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a…
ce:review
Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.
ce:compound-refresh
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, consolidating, replacing, or deleting them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/…
ce:compound
Document a recently solved problem to compound your team's knowledge.
ce:work
Execute work efficiently while maintaining quality and finishing features.
onboarding
Generate or regenerate ONBOARDING.md to help new contributors understand a codebase. Use when the user asks to 'create onboarding docs', 'generate ONBOARDING.md', 'document this project for new developers', 'write onboarding documentation', 'vonboard', 'vonboarding', 'prepare this repo for a new contributor', 'refresh…