What is cartographer-implement-plan?

A workflow for implementing several approved GitHub plan issues, where a plan issue records the agreed design and work. It orders the work, delegates each plan in an isolated copy of the repository, reviews the results, and merges them in sequence.

Use it to turn approved plans into pull requests, review those changes, and merge the completed work in the required order.

It prevents unapproved plans from being implemented and reduces conflicts when multiple changes are being delivered. It also keeps each piece of work separated until it has been reviewed.

How BeppeTemp/cartographer configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/BeppeTemp/cartographer/main/.claude/skills/cartographer-implement-plan/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/BeppeTemp/cartographer

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/beppetemp/cartographer/cartographer-implement-plan/github.svg)](https://agentmods.dev/skills/beppetemp/cartographer/cartographer-implement-plan)

Your own site

<a href="https://agentmods.dev/skills/beppetemp/cartographer/cartographer-implement-plan"><img src="https://agentmods.dev/badge/skills/beppetemp/cartographer/cartographer-implement-plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/beppetemp/cartographer/cartographer-implement-plan"><img src="https://agentmods.dev/badge/skills/beppetemp/cartographer/cartographer-implement-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,773 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00089	$0.03773
Opus 5.5	$0.00036	$0.01509
Sonnet 5.5	$0.00018	$0.00755
Haiku 4.5	$0.00009	$0.00377

Measured today against content hash a619c4332e8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cartographer-implement-plan 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 today.

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.

.claude/skills/cartographer-implement-plan/SKILL.md · 194 lines

How it starts

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

cartographer-implement-plan — plan issues → merged PRs

Source of truth is CONTRIBUTING.md §Plan issues + §Pull requests, AGENTS.md (workflow and delegation rules), and docs/index.md §Documentation maintenance rules. The cartographer-propose-plan skill covers writing and consuming a single plan. This skill adds only the multi-plan orchestration and the PR/merge cycle — read those first; do not duplicate them here.

The git work lives in make targets, not in prose.

Role

Before anything else, find your role (D955; CONTRIBUTING.md §Working with an agent client):

gh repo view "$(scripts/upstream-repo.sh)" --json viewerPermission --jq .viewerPermission

ADMIN, MAINTAIN or WRITE is maintainer mode; TRIAGE, READ, or any failure to read it, is contributor mode. State the mode to the user in one line.

Only an approved plan is implemented, in either mode, the maintainer's own plans included: select with --label plan --label approved. A plan the user names that lacks approved is not implemented: say it awaits a maintainer's approval. In contributor mode the plan must also be assigned to you (comment on it to claim it; the maintainer assigns it): plan-gate rejects the PR otherwise. Never add the label on your own initiative, only when the maintainer tells you to in this session.
Contributor mode: exactly one plan, no waves (§1 is skipped); the branch is pushed to origin, your fork. No gh pr merge, no armed auto-merge (§4 step 4 is skipped), no force-push you were not asked for. The skill ends with the PR open and its ## Self-review section filled.
Maintainer mode: unchanged from here on.

Preconditions

main is protected: every plan lands via its own PR, squash-merge, CI green. No direct pushes.
Merging a self-authored PR and git push --force-with-lease require an explicit user decision or a standing approval (the user's own Claude Code permission settings, e.g. Bash(gh pr merge *), Bash(git push --force-with-lease *), or .claude/settings.local.json). Never work around the approval gate — surface it and let the user choose.

Read the full file on GitHub · 194 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.

today Changed a619c4332e8e
2d ago Changed 7d5818750806
6d ago Changed 72d0cb580eb8
8d ago First seen · 194 lines · 89 tokens per session scan A 9f409fac76bc

Subscribe to this mod's changes

cartographer-implement-plan is a skill published in the GitHub repository BeppeTemp/cartographer (50 stars, last pushed today), licensed Apache-2.0. It adds 89 tokens to every session and 3,773 once invoked, about $0.0004 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-22.

Commits Git and workflow Project management agent-memory ai-agents go knowledge-base llm-agents mcp

GitHub Issue and PR Workflow

List and search issues, PRs, commits; summarize status and reviews.

djinilabs/helpmaton · 21 tokens

gsd-quick

Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.

SpillwaveSolutions/agent-brain · 24 tokens

gh-issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…

the-open-agent/openagent · 116 tokens

cartographer: Skill for Claude Code