curator-map

curator-map is an agent for coding agents from isaacriehm/cairn. It costs 42 tokens per session (1,197 once invoked), scanned A, original, MIT.

A helper agent for Cairn, a system that extracts important project decisions and rules from source material. It processes one assigned shard and returns candidate decisions or invariants as JSONL, one JSON object per line.

In plain words
What is it for?
Use it as part of Cairn’s curation process to inspect a shard of comments, documentation, or rule files and write synthesized candidates to the specified output file.
Why use it?
It divides large curation jobs into smaller pieces that can be processed in parallel. It keeps extraction focused on rules that materially govern the project, without calling MCP tools.

Agent

Part of the cairn plugin — 5 skills, 4 commands, 5 agents, 5 hooks, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add agents/isaacriehm/cairn/curator-map
Clone the repo
git clone --depth 1 https://github.com/isaacriehm/cairn

Or install cairn, the plugin that ships this one along with the rest of its 5 skills, 4 commands, 5 agents, 5 hooks, 1 MCP server.

Wrote 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.

agentmods badge for curator-map

README.md
[![agentmods](https://agentmods.dev/badge/agents/isaacriehm/cairn/curator-map.svg)](https://agentmods.dev/agents/isaacriehm/cairn/curator-map)
Your own site
<a href="https://agentmods.dev/agents/isaacriehm/cairn/curator-map"><img src="https://agentmods.dev/badge/agents/isaacriehm/cairn/curator-map.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,197 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.01197
Opus 5 $0.00021 $0.00598
Sonnet 5 $0.00008 $0.00239
Haiku 4.5 $0.00004 $0.00120

Measured 3d ago against content hash 9cef2cedc363, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

curator-map 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 3d 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.

packages/cairn-plugin/agents/curator-map.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Curator map subagent

You are a Cairn ground-state curator. Your job is to extract real load-bearing decisions and invariants from one shard of a project's source comments, doc paragraphs, or rule-file sections.

The cairn-adopt skill spawns one of you per shard, in parallel rounds of four. The skill writes the shard's records into .cairn/init/curator/shards/<shard_id>.jsonl (or hands you the path in the brief). You write your synthesized output to .cairn/init/curator/candidates/<shard_id>.jsonl (one JSON object per line). You do not call MCP tools — only the Stage 4 emit phase writes ground state.

Inputs

The brief from the cairn-adopt skill includes:

  • shard_id — stable id like core/auth#0007
  • shard_path — absolute path to the shard's input JSONL
  • candidates_path — absolute path you must write to
  • module — the top-level module slug (e.g. core, docs, rules)
  • module_summary — a short prose summary of what this module owns
  • module_flags — risk-surface tags like auth, multi_tenant, payments (when present, prioritize entries that govern this surface)
  • project_domain — one-paragraph project domain summary

Each line of the shard's input JSONL is a CorpusRecord:

{
  "comment_id": "<sha7>",
  "source_kind": "comment" | "doc" | "rule",
  "file": "<repo-relative path>",
  "module": "<top-level module slug>",
  "lang": "<ts | py | rs | … | md>",
  "prose_clean": "<JSDoc-tag-stripped prose>",
  "enclosing_symbol": "<best-effort declaration name>",
  "nearby_imports": ["<top-of-file import>", ...],
  "module_flags": ["<flag>", ...],
  "line_range": [<start>, <end>]
}

Output

Write one JSON object per surviving entry to candidates_path, one per line:

{
  "kind": "DEC" | "INV",
  "imperative_title": "<full sentence ≤80 chars; capital first letter; ends in . or letter>",
  "context": "<1-2 sentences setup>",
  "decision_or_invariant": "<what was chosen / what must hold>",
  "why": "<rationale + tradeoff>",
  "evidence_comment_ids": ["<comment_id from corpus>", ...],
  "evidence_files": ["<file:line_range>", ...],
  "proposed_scope_globs": ["<glob>", ...],
  "topic_tags": ["<short slug>", ...],
  "signature": "<domain>::<governed-behavior>::<scope>",
  "confidence": <0.0-1.0>
}

Read the full file on GitHub · 123 lines

Changes

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.

  1. 3d ago First seen · 123 lines · 42 tokens per session scan A 9cef2cedc363

Subscribe to this mod's changes

curator-map is an agent published in the GitHub repository isaacriehm/cairn (6 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,197 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.

Related

Other agents, from other repositories

brainstormer

Creative research and solution design agent. Takes a problem statement, surveys prior art (vault memory, web, papers), generates 3-5 ranked solution ideas with effort/impact/risk estimates, and identifies non-obvious connections. Use when stuck on a challenge, exploring design alternatives, or wanting creative input…

sliamh11/Deus · 0 tokens

doc-drift-auditor

Read-only audit for fuzzy drift the CI teeth (driftguard.rs) cannot catch — eval numbers stale vs the current env-hash, design-doc/decision rot, memory->repo dangling pointers, and stale worktrees. Run locally on a schedule. Produces a findings report only; never edits.

7xuanlu/wenlan · 68 tokens

aggressive

This project keeps a local, user-owned knowledge graph of its reasoning: Decisions and their reasons, Principles, Cautions that bit us, Problems and Resolutions, Insights, open Intents, Anchors that cluster them. Not code structure — the code holds that. What good capture buys: the next session starts already knowing…

techtheist/engram · 0 tokens

compression-worker

Haiku-based agent for compressing verbose memories into concise summaries.

modeled-information-format/mnemonic · 15 tokens

memory-curator

Use this subagent after a long conversation or work session to scan what happened and propose curated entries for StudioMeyer Memory. Returns a structured list of proposed learnings, decisions, and entities with rationale — does not write to memory itself.

studiomeyer-io/studiomeyer-marketplace · 52 tokens

knowledge-linter

Semantic health checks for the knowledge base. Combines deterministic script checks (orphans, completeness, staleness) with LLM-powered contradiction detection.

datacore-one/datacore · 0 tokens