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-verifynpx skills add knowns-dev/knowns --skill kn-verifygit 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-verify)<a href="https://agentmods.dev/skills/knowns-dev/knowns/kn-verify"><img src="https://agentmods.dev/badge/skills/knowns-dev/knowns/kn-verify.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.00013 | $0.01504 |
| Opus 5 | $0.00006 | $0.00752 |
| Sonnet 5 | $0.00003 | $0.00301 |
| Haiku 4.5 | $0.00001 | $0.00150 |
Grade A, and why
kn-verify 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Verification
Run validation with SDD-awareness to check spec coverage and task status.
Announce: "Using kn-verify to check SDD status."
Core principle: VERIFY SPEC COVERAGE → REPORT WARNINGS → SUGGEST FIXES.
Inputs
- Entire project SDD state, or a narrower entity if the user asked for focused validation
Verification Rules
- Report concrete warnings before general commentary
- Prefer actionable fixes over generic advice
- Separate coverage problems from broken refs or missing links
- Require complete
Spec Decision Compliancemarkers for in-review/done linked tasks; any conflict is a validation failure - Require every in-review/done linked task to record exactly one valid impact branch:
System Decision Impact: none — <reason>creates no candidateSystem Decision Impact: candidate @decision/<id> (added|changed|removed) — <summary>resolves to a persisted non-current candidate linked to originating work
- Keep unverified draft/replacement Decisions out of current guidance
- Keep Spec Decisions canonical in the spec's
Locked Decisionssection; ledger duplication is a validation failure - Treat new Memory category
decisionas legacy workflow drift and require first-class Decision capture instead - When gathering context, retrieve only relevant accepted/current System Decisions with bounded filters; do not serialize all Decisions
Step 1: Run SDD Validation
Via CLI
knowns validate --sdd --plain
Via MCP (if available)
mcp_knowns_validate({ "scope": "sdd" })
Step 2: Present SDD Status
Return the verification result using the shared output contract:
- Goal/result: whether SDD validation passed, failed, or surfaced warnings
- Key details: coverage summary, explicit warnings, passing checks, and the highest-priority fixes
- Next action: only when the warnings point to a clear follow-up command
The key-details portion may include a compact status block such as:
Specs: X total | Y approved | Z draft
Tasks: X total | Y done | Z in-progress | W todo
Coverage: X/Y tasks linked to specs (Z%)
Warnings:
- task-XX has no spec reference
- specs/feature: X/Y ACs incomplete
Passed:
- All spec references resolve
- specs/auth: fully implemented
- Spec Decisions: all linked D-IDs assessed with no conflicts
- System Decision Impact: declared and lifecycle-valid
- System Decision Impact refs: persisted with task/spec/source provenance
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 · 175 lines · 13 tokens per session scan A 7f481b3bdde3
kn-verify is a skill published in the GitHub repository knowns-dev/knowns (242 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 1,504 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.