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-templatenpx skills add knowns-dev/knowns --skill kn-templategit 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-template)<a href="https://agentmods.dev/skills/knowns-dev/knowns/kn-template"><img src="https://agentmods.dev/badge/skills/knowns-dev/knowns/kn-template.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.00017 | $0.00964 |
| Opus 5 | $0.00009 | $0.00482 |
| Sonnet 5 | $0.00003 | $0.00193 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
kn-template 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working with Templates
Announce: "Using kn-template to work with templates."
Core principle: USE TEMPLATES FOR CONSISTENT CODE GENERATION.
Inputs
- Template name or generation goal
- Variables required by prompts
- Linked pattern doc, if one exists
Preflight
- Read the linked doc before running a non-trivial template
- Use dry run before generating real files
- Check whether a template already exists before creating a new one
Step 1: List Templates
mcp_knowns_templates({ "action": "list" })
Step 2: Get Template Details
mcp_knowns_templates({ "action": "get", "name": "<template-name>" })
Check: prompts, doc: link, files to generate.
Step 3: Read Linked Documentation
mcp_knowns_docs({ "action": "get", "path": "<doc-path>", "smart": true })
Step 4: Run Template
// Dry run first
mcp_knowns_templates({ "action": "run", "name": "<template-name>",
"variables": { "name": "MyComponent" },
"dryRun": true
})
// Then run for real
mcp_knowns_templates({ "action": "run", "name": "<template-name>",
"variables": { "name": "MyComponent" },
"dryRun": false
})
Step 5: Create New Template
mcp_knowns_templates({ "action": "create", "name": "<template-name>",
"description": "Description",
"doc": "patterns/<related-doc>"
})
Template Config
Use the current template schema returned by templates({ action: "get" }). A minimal example:
name: react-component
description: Create a React component
doc: patterns/react-component
prompts:
- name: name
type: text
message: Component name?
validate: required
actions:
- type: add
template: component.tsx.hbs
path: src/components/{{pascalCase name}}.tsx
skipIfExists: true
Syntax Rules
- Use the template engine's documented
{{helper value}}expressions directly. - Do not construct template delimiters through string concatenation or add JavaScript interpolation syntax around them.
- Validate helper names and output paths with a dry run before writing files.
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 · 139 lines · 17 tokens per session scan A 82a3792324fa
kn-template is a skill published in the GitHub repository knowns-dev/knowns (241 stars, last pushed 7d ago), licensed MIT. It adds 17 tokens to every session and 964 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…
mnemo-cortex
Installs and wires Mnemo Cortex (local-first persistent memory) into OpenClaw and other MCP-capable agents. Use for cross-session recall, decision history, or multi-agent shared memory.