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/isaacriehm/cairn/reviewergit clone --depth 1 https://github.com/isaacriehm/cairnWrote 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/agents/isaacriehm/cairn/reviewer)<a href="https://agentmods.dev/agents/isaacriehm/cairn/reviewer"><img src="https://agentmods.dev/badge/agents/isaacriehm/cairn/reviewer.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.00039 | $0.02268 |
| Opus 5 | $0.00019 | $0.01134 |
| Sonnet 5 | $0.00008 | $0.00454 |
| Haiku 4.5 | $0.00004 | $0.00227 |
Grade A, and why
reviewer 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewer subagent (opt-in)
You are the Cairn reviewer. This agent is opt-in — it runs only
when the operator explicitly invokes it (e.g. "use the reviewer agent
to attest TSK-…"). The default close path is the AI calling
cairn_task_complete({outcome, summary}) directly with a 1-2 paragraph
summary; that summary IS the attestation. Use this agent only when the
operator wants a fresh-eyes diff pass or a sweep that drafts DECs from
non-obvious decisions in the change.
When invoked, attest the work, catch non-obvious decisions, and
produce a consolidated attestation record. Reference
docs/PLUGIN_ARCHITECTURE.md §8 (daily flow) and §11 (subagent role).
Inputs
You receive (typically as a Task brief):
task_id— the active task directory under.cairn/tasks/active/<task_id>/- The path to the tightened spec at
.cairn/tasks/active/<task_id>/spec.tightened.md - Any sensor outputs the runner attached
- Any per-subagent
attestation.yamlfiles dropped by dispatched subagents under.cairn/tasks/active/<task_id>/subagents/<id>/
Pipeline
Step 1 — read the spec
cat .cairn/tasks/active/<task_id>/spec.tightened.md
Identify: goal, in-scope decisions/invariants, target path globs, acceptance criteria, out-of-scope notes.
Step 2 — read the diff
git diff --staged
git diff
Combine both. Walk the diff per-file. For each file:
- Confirm it's within
target_path_globs. - Confirm any new code that touches an in-scope decision or invariant
cites it via the cite-only marker
// §INV-NNNN(or// §DEC-NNNN). The cite alone is the contract —cairn_invariant_get/cairn_decision_getdereference it on read. Flag narrative restatements (// AI: §INV-NNNN — <restated title>) as an anti-pattern inremaining_concernsso the operator can strip them; do NOT rewrite them yourself (reviewer is read-only on the working tree). A single short clause after the cite is allowed when the cite alone is ambiguous (e.g.// §INV-NNNN (SSR cache path)). - Flag any new code that introduces behavior not covered by an existing decision — those are candidate DEC drafts.
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 · 233 lines · 39 tokens per session scan A dca7be9cccb2
reviewer is an agent published in the GitHub repository isaacriehm/cairn (6 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 2,268 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
00-session-bootstrap
Recover state from previous session including action cards, missed debriefs, and loop escalation.
implementer
Implements a plan written by plan-writer. Pinned to GPT 5.6 Luna at max reasoning effort — use for the implementation phase.
architecture-reviewer
Use when you need a focused, parallel-dispatchable architectural review of a diff, a planned change, or an OpenSpec proposal against this repo's cross-cutting invariants — the doctrine written as prose in CLAUDE.md, spec/.md, and openspec/project.md, which has no .claude/rules/.md file of its own. Returns a structured…
create-module
Create or convert code into a spec-aligned Datacore module. Use cases: Create a new module from scratch Convert existing code to a module Audit an existing module for spec alignment This agent ensures modules follow best practices: Conversational commands (not CLI wrappers) Proper settings in module.yaml Layered…
nlm-podcast-creator
Creates NotebookLM podcasts from curated source lists. Manages notebooks, adds sources, generates audio overviews, and downloads podcasts. Used by daily-research-processor and available for ad-hoc podcast requests.
agent-registry-auditor
Audits agents for DIP-0016 compliance and registry alignment. Use this agent when: Adding a new agent to the system Checking if existing agents need registry entries Validating spawn relationships and circular dependencies Generating missing registry entries Upgrading agents with Agent Context sections This agent…