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-gonpx skills add knowns-dev/knowns --skill kn-gogit 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-go)<a href="https://agentmods.dev/skills/knowns-dev/knowns/kn-go"><img src="https://agentmods.dev/badge/skills/knowns-dev/knowns/kn-go.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.00030 | $0.01097 |
| Opus 5 | $0.00015 | $0.00549 |
| Sonnet 5 | $0.00006 | $0.00219 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
kn-go 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 5d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Mode — Legacy Full Pipeline
Announce: "Using kn-go for spec [name]."
Core principle: APPROVED SPEC → TASKS → PLAN → IMPLEMENT → VERIFY → COMMIT GATE.
kn-go is a compatibility workflow. Use it only when the user explicitly requests the legacy no-review-gates pipeline. For normal approved-spec execution, delegation, parallel safety checks, or integrated review, use /kn-flow @doc/<spec-path>.
Inputs
- Approved spec ref
- Optional
--dry-runto validate and preview tasks without mutating project state
Stop if the spec is draft, has no ACs, has blocking open questions, or the requested ref cannot be resolved.
Phase 1: Validate and Discover
- Read the spec and its complete
Locked Decisionssection. - Validate the spec.
- Resolve existing linked tasks before generating anything.
- Reuse existing tasks; skip done tasks and continue todo/in-progress work in dependency order.
- Retrieve only relevant accepted/current System Decisions with bounded filters.
mcp_knowns_docs({ "action": "get", "path": "<spec-path>", "smart": true })
mcp_knowns_validate({ "entity": "<spec-path>" })
mcp_knowns_search({ "action": "resolve", "ref": "@doc/<spec-path>{implements}",
"direction": "inbound", "entityTypes": "task" })
With --dry-run, stop after presenting validation plus the task create/reuse preview.
Phase 2: Create Missing Tasks
Use the same task-shaping rules as /kn-plan --from @doc/<spec-path>, but skip its approval gate because the user explicitly selected go mode:
- clean titles and stable
order; no synthetic[<slug>-NN]bracket prefixes - the spec's optional
Task Generation→Task Prefixpassed asprefixon each create call, or omitted when blank to use the project default speclink andfulfillsmapping- outcome-oriented task ACs
- concise descriptions; implementation detail belongs in task plans
- no duplicate task scope
Report the number of reused and created tasks before implementation begins.
Phase 3: Execute Sequentially
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.
- 5d ago First seen · 115 lines · 30 tokens per session scan A 9d44d1221ed7
kn-go is a skill published in the GitHub repository knowns-dev/knowns (242 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,097 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.
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…
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…
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…
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.