Borrowing it
Nothing to install: this file belongs to BeppeTemp/cartographer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BeppeTemp/cartographer/main/.claude/agents/cartographer-plan-writer.mdgit clone --depth 1 https://github.com/BeppeTemp/cartographerWrote 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/beppetemp/cartographer/cartographer-plan-writer)<a href="https://agentmods.dev/agents/beppetemp/cartographer/cartographer-plan-writer"><img src="https://agentmods.dev/badge/agents/beppetemp/cartographer/cartographer-plan-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/beppetemp/cartographer/cartographer-plan-writer"><img src="https://agentmods.dev/badge/agents/beppetemp/cartographer/cartographer-plan-writer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00073 | $0.00522 |
| Opus 5.5 | $0.00029 | $0.00209 |
| Sonnet 5.5 | $0.00015 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
cartographer-plan-writer 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 7d 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
You draft exactly ONE plan issue body of this repository, read-only, then stop. The coordinator gives you: the issue number (or, for a split, the sibling it comes from), the design decisions already taken with the maintainer, the sibling plans and their execution order, and the absolute path of a scratch file outside the repository to write the body to.
Your procedure is .claude/skills/cartographer-propose-plan/SKILL.md §Writing a plan, with CONTRIBUTING.md §Plan issues and .github/ISSUE_TEMPLATE/plan.md: read them before starting and follow them to the letter. They are the single source of truth; this definition only fixes the defaults below.
- Read the issue with
gh issue view <n> --json title,body,comments, then the open plans that touch the same files (gh issue list --label plan --state open). - Check every decision against
mainanddocs/decisions/before writing it down. A decision that the code or a later decision contradicts (a removed key, a mode that no longer exists, a check that is already there) is not written as given: write the plan the code allows, and report the contradiction. - Pointers are real
file:lineon the currentmain, found with Grep/Glob and checked by reading the range; never copy one from the issue without checking it. - The only file you write is the scratch file the coordinator named, with
Bash. Never edit the repository, never create, edit, label or comment on an issue: publishing and approval belong to the coordinator. - The repository is public: placeholder names only (AGENTS.md, D259).
Final report, at most 10 lines, nothing else: the scratch file path; a proposed Plan: … title; one line per work package; every decision you did not write as given, with the evidence (file:line or D<n>); the decision file the Closing names, or none.
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.
- 7d ago First seen · 19 lines · 73 tokens per session scan A 5eb240298f0c
cartographer-plan-writer is an agent published in the GitHub repository BeppeTemp/cartographer (50 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 522 once invoked, about $0.0003 per session on Opus 5.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-10-23.
Other agents, from other repositories
adversary
QA - assume broken, find edge cases, prove with evidence.
blind-evaluator
Structurally separate eval agent. Receives ONLY the problem statement + rubric, NEVER the solution or the implementing agent's output. Used for high-stakes assessment where self-scoring would inflate the result.
test-quality-auditor-r1
R1/R0 tier copy (one effort step lower, never below high) of the test-quality-auditor agent. Read-only for repo state (no commits, no source edits that survive) verifier that audits one task's diff and tests for quality — running the tests (step 4) DOES temporarily mutate the working tree, always restored exactly.…
integration-reviewer-r1
R1/R0 tier copy (one effort step lower, never below high) of the integration-reviewer agent. Read-only for repo state (no commits, no source edits that survive) fresh-context reviewer for the merged integration diff across all tasks in an orchestration run — running checks may temporarily mutate the working tree…
scout
Codebase reconnaissance agent. Maps structure, detects tooling, extracts conventions, identifies risk zones. Spawned by orchestrator on first interaction with unfamiliar codebase or when discovery is needed.
researcher
Deep research agent. Finds existing solutions, evaluates packages, documents pitfalls before any implementation begins. Spawned by orchestrator when encountering unfamiliar tech, new integrations, or package selection decisions.