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-recordnpx skills add BANANASJIM/openplan-skill --skill openplan-recordgit 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-record)<a href="https://agentmods.dev/skills/bananasjim/openplan-skill/openplan-record"><img src="https://agentmods.dev/badge/skills/bananasjim/openplan-skill/openplan-record.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.00106 | $0.00829 |
| Opus 5 | $0.00053 | $0.00415 |
| Sonnet 5 | $0.00021 | $0.00166 |
| Haiku 4.5 | $0.00011 | $0.00083 |
Grade A, and why
openplan-record 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenPlan Record
Use this after $openplan-core when conversation, review, or implementation output needs to become durable memory or documentation.
Core Principle
Memory and docs represent the human goal/intent. Do not record agent guesses as the human goal/intent. If the source is not explicit, mark it as inference or pending confirmation.
Record Types
| Type | Purpose | Lifetime | Examples |
|---|---|---|---|
| Memory | Standing human preference or operating constraint | Long-lived, compact | "Do not checkout without permission", "docs in Chinese" |
| Docs | Project source of truth and rationale | Long-lived, structured | architecture, workflow, ADR, conventions |
| Handoff | Cross-agent/session continuity | Short/medium-lived | current objective, blockers, next safe action |
| Review | Evidence-backed quality finding | Snapshot | blocking issue, residual risk |
| HTML brief | Temporary human frontend | Disposable | visual summary, teaching page |
Update Flow
- Classify the information:
- explicit human goal/intent;
- agent observation;
- evidence-backed project fact;
- temporary session state;
- unresolved question.
- Choose destination:
- durable preference -> memory;
- project rule/rationale -> docs;
- current continuation state -> handoff;
- quality issue -> review;
- human-facing visualization -> HTML brief.
- Resolve destination root:
- memory location from platform or user instruction;
- docs root such as
.openplan/,docs/, repo root, separate docs repo, or user-provided path; - temporary output path for disposable briefs.
- Preserve provenance:
- source statement or artifact;
- date/session when useful;
- confidence;
- scope.
- Deduplicate before adding.
- Mark stale or superseded entries instead of silently overwriting when history matters.
- Before changing durable goal/intent from ambiguous input, ask only if this agent is the human-facing coordinator; otherwise report
Human decisions required.
What ships with it
4 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 · 93 lines · 106 tokens per session scan A be73baf19ab7
openplan-record is a skill published in the GitHub repository BANANASJIM/openplan-skill (4 stars, last pushed 3mo ago), licensed MIT. It adds 106 tokens to every session and 829 once invoked, about $0.0005 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.