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/bananasjim/openplan-skill/openplan-corenpx skills add BANANASJIM/openplan-skill --skill openplan-coregit clone --depth 1 https://github.com/BANANASJIM/openplan-skillWrote 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/bananasjim/openplan-skill/openplan-core)<a href="https://agentmods.dev/skills/bananasjim/openplan-skill/openplan-core"><img src="https://agentmods.dev/badge/skills/bananasjim/openplan-skill/openplan-core.svg" alt="Measured on agentmods" 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 | $0.00082 | $0.00792 |
| Opus 5 | $0.00041 | $0.00396 |
| Sonnet 5 | $0.00016 | $0.00158 |
| Haiku 4.5 | $0.00008 | $0.00079 |
Grade A, and why
openplan-core 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenPlan Core
Use this as the base layer for other OpenPlan-style skills. It is deliberately independent of any project-specific enforcement tooling or single agent platform.
Terminology: goal and intent are both valid. Use goal when emphasizing the desired outcome and verification. Use intent when emphasizing the human meaning, motivation, or decision behind that outcome.
Core Invariants
- Minimal effective context: load only what changes the next decision or review.
- Human-owned decisions: agents may suggest and execute, but humans own acceptance, bypass, scope, and tradeoff decisions.
- Externalized state: ground claims in files, diffs, reports, logs, or other durable artifacts, not chat memory.
- Layered authority: goal/intent and design constrain specs/plans; specs/plans constrain execution; execution does not silently rewrite the goal/intent.
- Dual-surface separation: when a project separates design/docs from implementation/code, preserve that separation and do not let execution redefine the source of truth.
- Dispatcher boundary: only the active human-facing coordinator asks the human; subagents report
Human decisions requiredorBLOCKEDinstead. - Role separation: alignment, research, design, implementation, testing, review, recording, gardening, and handoff are different modes even when one agent performs them.
- Evidence before confidence: every important claim needs observable support.
- Reversible automation: prefer actions that can be inspected, interrupted, replayed, or rolled back.
- No silent approval: "no findings" is not approval; it is a scoped review result.
Enforcement Is Optional
Hooks, isolated workspaces, CI checks, and other enforcement layers can strengthen the philosophy, but they are not the philosophy itself. In a Codex or Claude Code skill, keep the invariants as behavior, evidence, and reporting even when enforcement is unavailable.
Composition
Use this skill with:
$openplan-autofor orchestrating automatic/YOLO workflows.$openplan-operatefor session initialization, behavior constraints, and subagent delegation.$openplan-alignfor ambiguity and requirement shaping.$openplan-researchfor bounded evidence gathering before design or execution.$openplan-docs-initfor governed documentation generation setup.$openplan-testfor proportional test evidence and regression proof.$openplan-reviewfor YOLO/auto-mode review.$openplan-handofffor cross-agent or cross-session snapshots.$openplan-html-brieffor temporary human-facing HTML summaries.$openplan-recordfor maintaining memory and documentation as human goal/intent records.$openplan-gardenfor semantic document gardening and goal/intent drift checks.
What ships with it
3 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.
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 · 60 lines · 82 tokens per session scan A f288c5e9f9b7
openplan-core is a skill published in the GitHub repository BANANASJIM/openplan-skill (4 stars, last pushed 3mo ago), licensed MIT. It adds 82 tokens to every session and 792 once invoked, about $0.0004 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
nhk-bootstrap
Bootstrap an NHK workspace when first-time setup is needed or any required instruction, routing, planning, governance, or archive surface is missing.
nhk-upkeep
Repair NHK drift when an established workspace's instruction, routing, planning, governance, archive index, or tracking descriptions no longer match reality.
nhk-archive
Archive one completed NHK workstream when the human has explicitly approved its active-to-archive transition.
welcome-to-nhk
Route NHK work when dependency readiness, instruction topology, foundation state, or lifecycle stage is unresolved.
scribe-integration
How to use Scribe MCP tools correctly — logging, docs, topology, bugs, file reading, search.
scribe-onboarding
Install and connect Scribe MCP — pip install, one-command Postgres bootstrap, host/plugin projection, and first-bind verification.