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-flownpx skills add knowns-dev/knowns --skill kn-flowgit 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-flow)<a href="https://agentmods.dev/skills/knowns-dev/knowns/kn-flow"><img src="https://agentmods.dev/badge/skills/knowns-dev/knowns/kn-flow.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.00038 | $0.02058 |
| Opus 5 | $0.00019 | $0.01029 |
| Sonnet 5 | $0.00008 | $0.00412 |
| Haiku 4.5 | $0.00004 | $0.00206 |
Grade A, and why
kn-flow 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Flow Orchestration
Coordinate an approved spec, linked task set, or explicit task wave from planning through implementation, review, and verification.
Announce: "Using kn-flow for spec/task wave [ref]."
Core principle: APPROVED SPEC/TASK WAVE -> SCHEDULE -> PLAN -> IMPLEMENT -> REVIEW -> VERIFY.
When to Use
- After
/kn-specapproves a spec and the user wants the work completed end to end - When the user says "do all tasks", "complete this spec", "orchestrate sub-agents", "run the whole flow", or similar
- When multiple linked tasks need dependency ordering, ownership boundaries, review, and combined verification
When NOT to Use
- Draft specs or unresolved product questions -> use
/kn-spec - A single task with an existing plan -> use
/kn-implement <id> - Creating tasks only, without execution -> use
/kn-plan --from @doc/<spec-path> - Tiny standalone work -> use
/kn-plan --new "<summary>"
Inputs
- Spec ref:
@doc/<spec-path>preferred - Task IDs: one or more explicit tasks for a task wave
- Optional:
--sequentialto force single-threaded execution - Optional:
--plan-onlyto stop after plans and schedule
Startup
- Start with Knowns MCP
initial. - Read
kn-plan,kn-implement, andkn-reviewbefore using their procedures. - Read the spec or each explicit task.
- For every linked spec, read the complete canonical
Locked Decisionssection and keep its stable D-IDs as execution gates. - Retrieve relevant accepted/current System Decisions with a feature/task query,
sourceTypes:["decision"],status:"accepted",includeHistorical:false, and a bounded limit. - Search first, then follow explicit refs and retrieve only relevant context.
- Do not manually edit Knowns-managed task or doc markdown.
Task Discovery
For a spec ref:
- Read the spec.
- List tasks linked to the spec.
- Read the spec's optional
Task Generation→Task Prefix; when tasks must be generated, pass it asprefixon each create call without changing project config. - Sort by
order, then title. Generated IDs are identity, not workflow ordering. - If no tasks exist, use
/kn-plan --from @doc/<spec-path>behavior to preview tasks. Ask before creating tasks unless the user explicitly approved task creation.
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 · 194 lines · 38 tokens per session scan A 8caabec5514e
kn-flow is a skill published in the GitHub repository knowns-dev/knowns (241 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 2,058 once invoked, about $0.0002 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.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
spk-mission-types
Explain Spec Kitty mission types, step contracts, action indices, and when to choose each mission workflow.
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…