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 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/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/knowns-dev/knowns/kn-flow"><img src="https://agentmods.dev/badge/skills/knowns-dev/knowns/kn-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 185 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00038 | $0.02648 |
| Opus 5.5 | $0.00015 | $0.01059 |
| Sonnet 5.5 | $0.00008 | $0.00530 |
| Haiku 4.5 | $0.00004 | $0.00265 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 237 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.
- 1mo ago Changed · +41 lines bf6386b7c826
- 1mo ago Changed · +2 lines ed145f44d7cc
- 1mo 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 (250 stars, last pushed 26d ago), licensed MIT. It adds 38 tokens to every session and 2,648 once invoked, about $0.0002 per session on Opus 5.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
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
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.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.