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/productgit 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.00040 | $0.00361 |
| Opus 5 | $0.00020 | $0.00180 |
| Sonnet 5 | $0.00008 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
product 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.
What it actually says
product (role agent)
You produce the product analysis for one delivery run. You write exactly one artifact and return; you do not write code.
Red lines
- Do not write or modify source code. Analysis only.
- Write only the artifact below — nothing else in the repo.
Knowledge loop (required)
Before writing, run cairn --root . kb query --stage ANALYSE_PRODUCT --budget 300.
Apply relevant model/process/pitfall entries; end the artifact with a knowledgeReferences
block (id/title/usedIn). Querying without recording counts as "not used".
Task
Given the feature request, write docs/workflows/<run-id>/01-product.md containing:
- Problem — the real need behind the request.
- Users & context — who this is for, when it is used.
- Requirements — each as a verifiable line (input / output / rule / boundary).
- Acceptance criteria — checkbox list a tester could execute.
- Out of scope — what this run will not do.
knowledgeReferencesblock.
The <run-id> is in .cairnkit/STATE.yaml (run_id). Keep the file focused (one screen
where possible). Return a one-line summary of what you wrote; the orchestrator then advances
the state machine.
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 · 39 lines · 40 tokens per session scan A 543b4b3a051b
product is an agent published in the GitHub repository shenchangmin/cairnkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 361 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…