Borrowing it
Nothing to install: this file belongs to hraness/direct. 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/direct/main/.agents/skills/plan-kb/SKILL.mdgit clone --depth 1 https://github.com/hraness/directWrote 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/direct/plan-kb)<a href="https://agentmods.dev/skills/hraness/direct/plan-kb"><img src="https://agentmods.dev/badge/skills/hraness/direct/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/direct/plan-kb"><img src="https://agentmods.dev/badge/skills/hraness/direct/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.00065 | $0.01323 |
| Opus 5.5 | $0.00026 | $0.00529 |
| Sonnet 5.5 | $0.00013 | $0.00265 |
| Haiku 4.5 | $0.00006 | $0.00132 |
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 24d 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 — 24 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:
wordcell 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:
wordcell list --root "$KB_ROOT" --where type=plan --sort area --json
wordcell search "the intended outcome" --root "$KB_ROOT" --json
If wordcell 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/wordcell 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.
- 24d ago Changed · +1 tokens per session 779cf3414dc6
- 1mo ago First seen · 123 lines · 64 tokens per session scan A e2f15e174c91
plan-kb is a skill published in the GitHub repository hraness/direct (2 stars, last pushed 15d ago), licensed MIT. It adds 65 tokens to every session and 1,323 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 24 lines, and is treated as a copy.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
analyze-market
Perform a market analysis for a product category or segment. Trigger on: market analysis, market size, TAM SAM SOM, market opportunity, industry analysis.
league-akari-shard-development
Use when creating, extending, refactoring, splitting, or reviewing League Akari main or renderer shards, including shard file organization, controller/loader/executor/handler boundaries, naming conventions, renderer TSX usage, platform guards, and public contract compatibility.
ax-agent-rlm
This skill helps an LLM generate correct AxAgent RLM/runtime code using @ax-llm/ax. Use when the user asks about RLM code execution, AxJSRuntime, contextFields, contextPolicy, liveRuntimeState, promptLevel, stage prompt controls, executorModelPolicy, maxRuntimeChars, agent.test(...), llmQuery(...), recursionOptions…
review
Comprehensive security and correctness audit. Use for review, deep review, thermo nuclear, or thermonuclear requests and branch or PR diff audits.