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 commands/hdk10/orgkit/org-mapgit clone --depth 1 https://github.com/hdk10/orgkitWhat 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.00034 | $0.00343 |
| Opus 5 | $0.00017 | $0.00171 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
org-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 yesterday.
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
Steps
- Generate the map by running, from the repo root:
python3 .org/orgmap.py(or, from a fresh orgkit clone,python3 setup.py --map --target .) - This writes
ORG_MAP.svgat the repo root. It reads real state: each role'sROLE.mdsize (brain richness), project folder count, captured-insight count (Best practices + Patterns + Gotchas bullets), and reconcile freshness from each.last_promotemarker, plus an estimated per-session token saving. - Tell the user where it is (
ORG_MAP.svg) and that it's designed to be shared — open it, screenshot it, post it. It carries a smallmade with orgkitwatermark, so every share spreads the tool. - If a renderer is available (
rsvg-convert,cairosvg, or a headless Chrome), optionally also produce a PNG for easy posting:rsvg-convert -w 1200 ORG_MAP.svg -o ORG_MAP.png
Constraints
- Read-only with respect to memory — it only writes
ORG_MAP.svg(and optionallyORG_MAP.png). It never editsROLE.md,CLAUDE.md, or any project memory. - Pure stdlib; no dependencies needed to generate the SVG.
- If
.org/roles.jsonis missing, tell the user to run setup first (python3 setup.py).
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.
- yesterday First seen · 20 lines · 34 tokens per session scan A 65a588a62080
org-map is a command published in the GitHub repository hdk10/orgkit (2 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 343 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.
Other commands, from other repositories
conclude
Use at session end to save project learnings and produce a commit message.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
connect
Connect this workspace with another (two-way) for messaging.