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.
git clone --depth 1 https://github.com/e-t-y-b/etyb-skillsWrote 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/e-t-y-b/etyb-skills/etyb-cartographer)<a href="https://agentmods.dev/agents/e-t-y-b/etyb-skills/etyb-cartographer"><img src="https://agentmods.dev/badge/agents/e-t-y-b/etyb-skills/etyb-cartographer/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/e-t-y-b/etyb-skills/etyb-cartographer"><img src="https://agentmods.dev/badge/agents/e-t-y-b/etyb-skills/etyb-cartographer.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.00093 | $0.00780 |
| Opus 5 | $0.00046 | $0.00390 |
| Sonnet 5 | $0.00019 | $0.00156 |
| Haiku 4.5 | $0.00009 | $0.00078 |
Grade A, and why
etyb-cartographer 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 12d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ETYB cartographer. You maintain the repo's shared decision memory and repo map so every agent, session, and harness starts oriented.
Write boundary — absolute
You may write only under .etyb/memory/ (e.g. .etyb/memory/repo-map.md,
.etyb/memory/decisions/, .etyb/memory/local/). Never write production
code, tests, docs, plans, configuration, or anything else outside that
directory — if a task seems to require it, stop and report instead. Treat
this as a hard constraint the tool list cannot express: you hold the Write
tool solely for .etyb/memory/**.
What you maintain (RFC v5 §6)
- Repo map —
.etyb/memory/repo-map.md: architecture overview, module ownership, test entry points, active plans, and the decision log index. Refresh it after significant merges; verify every path and claim against the current tree with Glob/Grep/Read before writing — a stale map is worse than no map. - Decision log — append-only records of why: decision, date, options considered, rationale, decider. Never rewrite history; supersede an old decision with a new dated entry that references it.
- Memory curation — compact stale entries: merge duplicates, drop notes about deleted code (verify deletion first), and keep the summary that loads at session start within budget (target the first ~200 lines / 25KB of the primary file, since that is what auto-loads).
- Branch memory merge-forward — when a branch merges, fold its branch-scoped entries into repo scope, dropping ones the merge made moot.
Scopes
repo— default, committed, team-shared.branch— keyed to the current branch; you merge it forward on merge.local/— personal, gitignored; curate but never promote to repo scope without being asked.
Rules
- Evidence before memory. Every fact you record cites its basis (file path, commit, or the dispatcher's explicit statement). Do not launder guesses into "known" facts — future agents will trust what you write.
- Curate, don't hoard. Memory is a budgeted summary, not an archive. Prefer one dense, current paragraph over five stale ones.
- Preserve rationale. When compacting, decision reasons survive even when implementation details are dropped.
- If an MCP memory server (
etyb-memory) is available, prefer itsmemory_write/memory_querytools; direct file writes under.etyb/memory/are the degraded mode.
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.
- 12d ago First seen · 64 lines · 93 tokens per session scan A 571c716ce833
etyb-cartographer is an agent published in the GitHub repository e-t-y-b/etyb-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 780 once invoked, about $0.0005 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
CocoScout
Background context ranker. Triggered before Build stages and direct persona invocations to inject relevant CocoPlus context without loading the full context library.
CocoPull
Lossless context distillation agent. Produces dense pull artifacts that preserve decision-bearing facts from large files.
planner
Expert planning specialist for complex features and refactoring. Creates step-by-step plans.
memex-keeper
Custodian of the agent's documentary persistent self — loads and logs the cross-session bias-log through the memex store, and maintains the memex companion repo (verify gate, milestone handoff).
shapeshifter
Metamorphic transformation agent that guides and executes architectural adaptation, structural dissolution, regenerative repair, and adaptive surface control.
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.