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 skills/beppetemp/cartographer/plannpx skills add BeppeTemp/cartographer --skill plangit 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/skills/beppetemp/cartographer/plan)<a href="https://agentmods.dev/skills/beppetemp/cartographer/plan"><img src="https://agentmods.dev/badge/skills/beppetemp/cartographer/plan.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.00052 | $0.00720 |
| Opus 5 | $0.00026 | $0.00360 |
| Sonnet 5 | $0.00010 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
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 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan — analysis → implementation handoff
The agent-neutral source of truth is CONTRIBUTING.md §Plan issues (procedure
- self-sufficiency test) and the issue structure in
.github/ISSUE_TEMPLATE/plan.md. Read both; this skill only adds the Codex-side glue.
Writing a plan
- Survey the open plans before designing, not just the code:
gh issue list --label plan --state open, then read the candidates that touch the same area. A request already covered by an open plan (or already implemented onmain) is reported back, not re-planned; a partial overlap means extending/amending the existing issue or stating the relationship (execution order, shared files) in the new one. - Reserve the next free D number. Inspect both implemented records
(
rtk proxy rg -o '^## D[0-9]+' docs/decisions/) and every plan issue title (rtk gh issue list --label plan --state all --limit 1000), then choose the next number above both maxima. An issue title reserves its number even before the entry exists. UsePlan: <title> (D<n>); the D entry is written at the end of implementation, not now: the plan is its draft. - Derive the real
file:linepointers before writing (targeted symbol grep/search): the plan contains pointers, not paraphrases. - Write the body (in English) to a scratch file following the template
structure, then:
gh issue create --title "Plan: <title> (D<n>)" --label plan --body-file <file>. - Apply the self-sufficiency test from
CONTRIBUTING.mdbefore submitting. - One analysis, several plans → every issue states the cross-plan execution order and which sibling plans touch the same files (those land strictly sequentially, never in parallel). Amend a plan by editing the issue body while nothing is implemented yet; once implementation starts, amend via comments only.
- Sibling cross-links: create the issues in execution order, then amend each
body to reference siblings as
D<n> (#<issue>)— the numbers exist only after creation. A pointer into a sibling's not-yet-implemented artifact cites the plan (D<n> WP<m>), never an inventedfile:line.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 52 lines · 52 tokens per session scan A 8348df87990e
plan is a skill published in the GitHub repository BeppeTemp/cartographer (17 stars, last pushed 6d ago), licensed Apache-2.0. It adds 52 tokens to every session and 720 once invoked, about $0.0003 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-30.
Other skills, from other repositories
loop-implement
The single implementation loop. It plans via wiki-plan (step 2, required) into an ordered, wiki-navigated task list, then executes those tasks in order, each loading only its named wiki pages, writing tests first, getting an independent test-quality audit, and judging against done; on failure it reflects and retries…
knowledge-flush
Drain queued ★ Insight candidates (harvested from your sessions) into the wiki as a reviewed PR. For each candidate it researches and verifies the best-practice against real sources, checks existing wiki layers for duplicates and links, decides the target layer/category (or justifies a new one), runs wiki-ingest, then…
wiki-plan
The fixed planning methodology for a capable model. Make every design decision grounded in a bundled wiki page (recording a decision-to-page map), then decompose the work into ordered, self-contained tasks, each naming the exact wiki pages that govern it. Runs as loop-implement step 2.
configure
Set up dev-loop's capability-role tool profile — map knowledge (your domain wiki / MCP), verify (your project's test/build/QA command), explore (code search), tacit (past incidents), and design (Figma/visual spec) to the actual tools this environment has, then write /.claude/dev-loop/tools.json (global) or…
fkf-use
Use an fkf base safely: inspect status, retrieve bounded context, resolve URIs, traverse declared relations, collect sources, or serve read-only MCP. Invoke for any read or collection workflow in a base.
fkf-learn
Promote verified fkf task-trace findings into a dated log, approved wiki concepts, or project pages. Invoke before closing a session that made a decision, changed behavior, or found a durable dead end.