Borrowing it
Nothing to install: this file belongs to hraness/wrench. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hraness/wrench/main/.agents/skills/plan-kb/SKILL.mdgit clone --depth 1 https://github.com/hraness/wrenchWrote 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/hraness/wrench/plan-kb)<a href="https://agentmods.dev/skills/hraness/wrench/plan-kb"><img src="https://agentmods.dev/badge/skills/hraness/wrench/plan-kb/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/hraness/wrench/plan-kb"><img src="https://agentmods.dev/badge/skills/hraness/wrench/plan-kb.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00064 | $0.01311 |
| Opus 5.5 | $0.00026 | $0.00524 |
| Sonnet 5.5 | $0.00013 | $0.00262 |
| Haiku 4.5 | $0.00006 | $0.00131 |
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 1mo 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.
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.
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 managedindex.mdfront door, then set the shell-localKB_ROOTto that path (KB_ROOT=kbfrom a typical repository root, orKB_ROOT=.from inside the vault). Read the vault'sAGENTS.mdand 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_REPOand 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>.mdunless the local guide already groups plans by area. Do not reorganize older plans merely to impose a new tree.
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.
- 1mo ago First seen · 123 lines · 64 tokens per session scan A e2f15e174c91
plan-kb is a skill published in the GitHub repository hraness/wrench (4 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,311 once invoked, about $0.0003 per session on Opus 5.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.
Other skills, from other repositories
gno
Search local documents, files, notes, and knowledge bases. Index directories, search with BM25/vector/hybrid, get AI answers with citations. Use when user wants to search files, find documents, query notes, look up information in local folders, index a directory, set up document search, build a knowledge base, needs…
atet
Use Atet to create, generate, record, edit, and render visual media with a local CLI and coding agent. Trigger for AI image or video generation, screen, camera, microphone, or system-audio recording, non-destructive video editing, silence and filler-word removal, captions or subtitles, speaker framing, screen zooms…
query-kb
Load scoped repository context, then search and navigate a hraness/kb Markdown vault with hybrid text retrieval, exact metadata, bounded links and typed relationships, backlinks, whole-vault graph reports, and optional Git provenance. Use when an agent needs the applicable repository instructions, rationale, prior…
save-url-kb
Capture public or signed-in web content into a local Markdown knowledge base as an auditable source bundle with local assets. Use when the user asks to clip, save, scrape, or archive an article, social post or thread, GitHub or Discourse discussion, feed, inbox, private document, WhatsApp conversation, YouTube page…
percolate-kb
Review a hraness/kb Markdown vault for recurring ideas and missing structural connections, then promote evidence-backed concepts and typed relationships with the KB CLI. Use after materially adding or revising notes, when organizing an accumulated vault, or when an agent needs to turn repeated tags and prose…
plan-kb
Create or evolve a durable Markdown plan inside a hraness/kb vault. Use when a user asks for an implementation plan, proposal, RFC, migration plan, execution audit, phased checklist, or an update to an existing plan's decisions, progress, review findings, verification evidence, or final result.