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/knowns-dev/knowns/kn-plannpx skills add knowns-dev/knowns --skill kn-plangit clone --depth 1 https://github.com/knowns-dev/knownsWrote 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/knowns-dev/knowns/kn-plan)<a href="https://agentmods.dev/skills/knowns-dev/knowns/kn-plan"><img src="https://agentmods.dev/badge/skills/knowns-dev/knowns/kn-plan.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.00012 | $0.01508 |
| Opus 5 | $0.00006 | $0.00754 |
| Sonnet 5 | $0.00002 | $0.00302 |
| Haiku 4.5 | $0.00001 | $0.00151 |
Grade A, and why
kn-plan 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 4d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Work
Core principle: GATHER CONTEXT → PLAN → VALIDATE → WAIT FOR APPROVAL.
Modes
/kn-plan <task-id>— plan an existing task/kn-plan --new "<summary>"— create a bounded task, then plan it/kn-plan --from @doc/<spec-path>— preview and create tasks from an approved spec
If the user wants end-to-end execution of an approved spec or task wave, route to /kn-flow @doc/<spec-path>.
Shared Preflight
- Read the primary task or spec before searching adjacent context.
- Follow every explicit
@task-,@doc/, and@template/ref recursively. - Read a linked spec's complete
Locked Decisionssection and enumerate every D-ID. - Retrieve only relevant accepted/current System Decisions with bounded filters.
- Search docs, memories, related tasks, and templates only as needed.
- Stop on a missing primary source, unreadable rule, broken critical ref, or concrete Decision conflict.
Existing Task Mode
Announce: "Using kn-plan for task [ID]."
- Read the task and confirm it is not already done unless reopening is intended.
- Take ownership and start its timer. If another timer cannot be safely paused or replaced, surface that conflict rather than silently changing it.
- Gather bounded context from refs, related docs/tasks, code patterns, memories, templates, and relevant Decisions.
- Draft an outcome-oriented implementation plan.
- Save the plan to the task.
- Validate the task and run the plan-quality checks below.
- Present the plan and wait for explicit approval before implementation.
mcp_knowns_tasks({ "action": "get", "taskId": "<id>" })
mcp_knowns_tasks({ "action": "update", "taskId": "<id>",
"status": "in-progress", "assignee": "@me" })
mcp_knowns_time({ "action": "start", "taskId": "<id>" })
New Task Mode
Announce: "Using kn-plan to create and plan a new task."
Classify the summary:
- tiny/normal: create a concise task, then continue with Existing Task Mode
- high-risk or broadly ambiguous: recommend
/kn-specunless the user explicitly bypasses it
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.
- 4d ago First seen · 164 lines · 12 tokens per session scan A be7dca5bf8d3
kn-plan is a skill published in the GitHub repository knowns-dev/knowns (242 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 1,508 once invoked, about $0.0001 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-30.
Other skills, from other repositories
agent-session-monitor
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage. Supports web interface for viewing complete conversation history and costs. Use when users ask about current session token consumption, conversation history, or cost statistics.
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…
fullenrich-content-engagers
Use when the user says "enrich people who engaged with this post", "qualify post engagers with FullEnrich", "scrape and enrich LinkedIn post {URL}", "engagers from this post into a CSV", "enrich this CSV of leads", "FullEnrich content engagers", or any variant indicating they want to convert a list of leads — either…
architecture-reviewer
Use when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles. Triggers include "review architecture", "check design", "does this fit", "where should this go", "planning a feature", or before…
enrich-with-signals
Pull PredictLeads buying-intent signals (jobs, news, funding, tech, leadership changes) for a result set of companies and write them back into the local cache. Use when the user says 'enrich these companies with signals', 'add buying signals to this list', 'pull intent data for [domain]', 'check signals for these…
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.