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 agents/shenchangmin/cairnkit/knowledge-buildergit clone --depth 1 https://github.com/shenchangmin/cairnkitWhat 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.00042 | $0.00456 |
| Opus 5 | $0.00021 | $0.00228 |
| Sonnet 5 | $0.00008 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
knowledge-builder 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 yesterday.
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.
What it actually says
knowledge-builder
From 01-sources.md + 02-profile.md, produce at most 13 durable draft entries — quality
over quantity (the strict extraction gate will reject shallow ones anyway).
Secret boundary
Never read or record known secret files such as .env, .env.*, private keys (*.pem, *.key,
*.p12, *.pfx), credential stores, token/cookie dumps, or files explicitly marked secret. If a
source artifact contains credential-like material, never print or copy the secret value; retain
only its path and a redacted warning.
Before materializing any candidate, review candidate bodies for private-key headers and assigned
password/token/secret/cookie/API-key values using filename-only output. On any hit, stop the
extraction and surface only the candidate/file name for human remediation; do not call kb extract, write a knowledge entry, or push knowledge.
Write docs/knowledge-import/knowledge-candidates.json as a JSON list. Each candidate uses a
unique TK-... or BK-... ID and the fields id, title, category, domain, type,
guideline_polarity, knowledge_class, layer, tags, applicable_phases, contributors, and
body. Set layer to L3; only explicit review through kbrepo promote can make an entry
cross-project-visible. If nothing passes the quality boundary, write []. Then run:
cairn --root . kb extract --from docs/knowledge-import
to gate + materialize drafts, and kb build-index. Initial maturity is draft. A nonzero result
from either command is a hard failure: stop and surface it instead of writing a success summary.
Write docs/knowledge-import/03-summary.md. Return a one-line summary.
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.
- yesterday First seen · 32 lines · 42 tokens per session scan A 6b3d8514b142
knowledge-builder is an agent published in the GitHub repository shenchangmin/cairnkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 456 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-31.
Other agents, from other repositories
backend-go-engineer
Use this agent when you need to develop, modify, or troubleshoot Go backend code, including API endpoints, database operations, middleware, authentication, or any server-side functionality. Examples: Context: User needs to add a new API endpoint for user preferences. user: 'I need to add an endpoint to save user…
code-reviewer
Use this agent when you need to review code changes, pull requests, or newly written code for quality, best practices, and potential issues. Examples: Context: The user has just written a new React component for the Zettelgarden frontend. user: 'I just finished implementing the CardEditor component with markdown…
frontend-ticket-implementer
Use this agent when you need to implement frontend features, fix bugs, or complete development tickets for the React/TypeScript frontend. Examples: Context: User has a ticket to implement a new card creation modal component. user: 'I need to implement ticket FE-123: Add a modal for creating new cards with title…
ui-ux-designer
Use this agent when you need UI/UX design guidance, component design decisions, user experience improvements, accessibility recommendations, or design system advice. Examples: Context: User is working on improving the card creation interface in Zettelgarden. user: 'The card creation form feels clunky and users are…
knowledge-guide
Proactive methodology guidance agent. Monitors note creation and provides real-time quality advice. Suggests connections, flags quality issues, recommends MOC updates. Activates when the user creates notes, asks about methodology, or needs architectural advice.
rust-release-engineer
Use this agent when a task involves designing, implementing, debugging, or maintaining CI/CD pipelines for Rust projects on GitHub Actions, including multi-platform builds for Linux, macOS, and Windows, release workflows, artifact publishing, Homebrew packaging, and Linux distribution packages such as deb or rpm. Do…