A skill for creating and maintaining implementation plans as Markdown files in a knowledge-base vault. A vault is a folder that stores organized notes and plans.

Writing implementation plans, proposals, RFCs, migration plans, phased checklists, and execution audits, or updating an existing plan with findings and verification evidence.

It keeps decisions, progress, checks, and final results in a durable document instead of leaving the plan only in a chat.

plan-kb — Skill by hraness

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/hraness/direct/plan-kb

Any agent

npx skills add hraness/direct --skill plan-kb

Clone the repo

git clone --depth 1 https://github.com/hraness/direct

Made for: Claude Code, Codex.

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,311 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00064	$0.01311
Opus 5	$0.00032	$0.00656
Sonnet 5	$0.00013	$0.00262
Haiku 4.5	$0.00006	$0.00131

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to plan-kb — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/plan-kb/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write a durable plan

Keep the plan useful before, during, and after execution. It is the coordination record, not a disposable answer or a duplicate task tracker.

Find the plan's owner

Resolve <vault> to the directory containing its authored or managed index.md front door, then set the shell-local KB_ROOT to that path (KB_ROOT=kb from a typical repository root, or KB_ROOT=. from inside the vault). Read the vault's AGENTS.md and the nearest guide under <vault>/plans/. Pass that resolved root to every command; do not assume the starting directory is the vault.
When the plan owns a repository path, resolve the repository root as KB_REPO and load that path's current memory before a whole-vault search:

kb context "<repository-path>" --root "$KB_ROOT" --repo "$KB_REPO"

Use --kind file or --kind directory when an absent future path cannot be classified from the filesystem. Read the inherited guides first, then the applicable maintained knowledge, active plans, dated research, reports, and separate historical-plan group.

Search existing plans before creating one:

kb list --root "$KB_ROOT" --where type=plan --sort area --json
kb search "the intended outcome" --root "$KB_ROOT" --json

If kb is not installed, do not let retrieval tooling block the plan: use rg or the available file search over <vault>/plans/, titles, aliases, and relevant terms. If the directory is not an initialized hraness/kb vault, follow the repository's existing planning convention instead of initializing one without being asked. Semantic search writes only a derived local cache; when that cache location is not writable, use exact search or point XDG_CACHE_HOME at a writable cache directory.

Update an existing plan when it already owns the outcome. Create a new file only for independently executable work.
Use <vault>/plans/<descriptive-kebab-name>.md unless the local guide already groups plans by area. Do not reorganize older plans merely to impose a new tree.

Read the full file on GitHub · 123 lines

Files

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.

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.

2d ago First seen · 123 lines · 64 tokens per session scan A e2f15e174c91

Subscribe to this mod's changes

plan-kb is a skill published in the GitHub repository hraness/direct (2 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 1,311 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to plan-kb, differing in 0 lines, and is treated as a copy.

Code review Frontend Testing ai-agents deterministic-testing frontend-testing scenario-testing testing-tools

keploy-docs

Guide for contributing to the Keploy documentation site at github.com/keploy/docs. Invoke when a change in keploy/keploy introduces, removes, or alters user-visible behavior (new CLI flag, changed default, new command, new configuration field, new on-disk format) and the docs need to catch up — or when the user asks…

keploy/keploy · 116 tokens

keploy-pr-workflow

Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.

keploy/keploy · 71 tokens

keploy-e2e-test

End-to-end verification of a change to keploy/keploy using keploy's own record/replay against a real sample application. Use whenever the user asks to test a change, verify a fix, prove that a modification works in practice, add e2e coverage for a PR, reproduce a bug against a sample app, or wire a behavior into CI.…

keploy/keploy · 118 tokens

plan-kb