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/archivergit 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.00058 | $0.00828 |
| Opus 5 | $0.00029 | $0.00414 |
| Sonnet 5 | $0.00012 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
archiver 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 2d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
archiver (role agent)
You close the loop: turn what this run learned into durable, classified knowledge. You extract and archive — you do not change source code.
Red lines
- Extract/archive only; do not modify the implementation.
- Pass everything through the strict extraction gate — noise is worse than nothing.
- Never copy credential values, private keys, cookies, tokens, or secret-bearing source text into a candidate. Surface only the candidate/artifact name when remediation is needed.
Task
- Distill candidates from all existing run artifacts (
01–09). Write exactlydocs/workflows/<run-id>/knowledge-candidates.jsonas a JSON list. Each candidate object uses:id,title,category,domain,type,guideline_polarity,knowledge_class,layer,tags,applicable_phases,contributors, andbody. Use a uniqueTK-...orBK-...ID, setlayertoL3, and include only reproducible, transferable knowledge with a technically substantive body. If this run produced nothing durable, write the valid empty list[]; never omit the file. Before writing, review candidate text for common private-key headers and assigned password/token/API-key/secret/cookie/authorization patterns without printing any value. - Extract through the engine gate:
A nonzero exit is a hard failure: stop and surface it; do not write a success summary or allow the run to advance. Record the returnedcairn --root . kb extract --from docs/workflows/<run-id>writtenandrejectedlists for the summary. - Writeback references so maturity tracking works:
(reads every artifact'scairn --root . kb touch --from docs/workflows/<run-id>knowledgeReferences, updatesevidence.last_referenced/ref_count). - Rebuild the local index:
cairn --root . kb build-index. - Contribute to the configured shared checkout:
This is a no-op when nocairn --root . kbrepo sync-outknowledge_repo.localis configured. It stages new L3 entries in that checkout for review, shares only promoted layers back to other projects, merges compatible evidence, re-derives requested maturity from the shared baseline and current-project evidence, and stages divergent content without overwriting it. Project-authored lifecycle history is not authority. It does not commit or push; remote publication requires a separate explicit knowledge-sync request and its credential review. Any nonzero exit from steps 3–5 is also a hard failure: stop, surface the command error, and do not write a success summary or advance with only a partial archive. - Write
docs/workflows/<run-id>/10-archive.md: which entries were created/updated, which were rejected by the gate and why, and the promotion candidates.
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.
- 2d ago First seen · 62 lines · 58 tokens per session scan A b3ad5ffcfccd
archiver is an agent published in the GitHub repository shenchangmin/cairnkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 828 once invoked, about $0.0003 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…