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 kdcokenny/ocx --skill plan-protocolgit clone --depth 1 https://github.com/kdcokenny/ocxWrote 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/kdcokenny/ocx/plan-protocol)<a href="https://agentmods.dev/skills/kdcokenny/ocx/plan-protocol"><img src="https://agentmods.dev/badge/skills/kdcokenny/ocx/plan-protocol/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/kdcokenny/ocx/plan-protocol"><img src="https://agentmods.dev/badge/skills/kdcokenny/ocx/plan-protocol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.01881 |
| Opus 5.5 | $0.00006 | $0.00752 |
| Sonnet 5.5 | $0.00003 | $0.00376 |
| Haiku 4.5 | $0.00001 | $0.00188 |
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 18d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- plan-protocol — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frozen V1 reference. This document is preserved from OCX
e79df6f. Its tool names, models, APIs, and installation instructions describe OpenCode V1. For the supported V2 setup, see the OCX 3 documentation.
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`
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.
- 18d ago Changed · +2 lines c30435f469f4
- 1mo ago First seen · 260 lines · 14 tokens per session scan A 3e2708c8c62e
plan-protocol is a skill published in the GitHub repository kdcokenny/ocx (978 stars, last pushed 18d ago), licensed MIT. It adds 14 tokens to every session and 1,881 once invoked, about $0.0001 per session on Opus 5.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
cli-builder
Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.
contract-integrity
Maintains an Agulater Agent Operational Contract after agent files change. Use when changing AGENTS.md, harness policy, graphs, skills, context layers, evaluation, or handoff behavior.
change-safety
Plans small software changes, protects existing work, and selects proportionate verification.
task-orientation
Turns a new request into a bounded task by selecting context, naming uncertainty, and defining verification. Use at the start of a new task or after a material task change.
evidence-synthesis
Builds research findings from inspected sources while preserving uncertainty and provenance.
imaging-data-commons
Query and download public cancer imaging data from NCI Imaging Data Commons using idc-index. Use for accessing large-scale radiology (CT, MR, PET) and pathology datasets for AI training or research. No authentication required. Query by metadata, visualize in browser, check licenses.