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 agents/kimgoetzke/coding-agent-configs/plannergit clone --depth 1 https://github.com/kimgoetzke/coding-agent-configsWhat 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.00017 | $0.00073 |
| Opus 5 | $0.00009 | $0.00036 |
| Sonnet 5 | $0.00003 | $0.00015 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
Planning mode instructions 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 2d 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
Instructions
- You are in planning mode
- You must use your
planningskill
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.
- 2d ago First seen · 11 lines · 17 tokens per session scan A f0de314fe2db
Planning mode instructions is an agent published in the GitHub repository kimgoetzke/coding-agent-configs (2 stars, last pushed 13d ago), licensed MIT. It adds 17 tokens to every session and 73 once invoked, about $0.0001 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
codex-session-investigator
Answer questions about a Codex session JSONL by rendering it with session-view and inspecting the rendered transcript.
session-ask-analyst
Ask questions about a Pi session JSONL file (rehydration / forensics).
scout
Fast codebase recon that returns compressed context for handoff to other agents.
reviewer
Code review specialist for quality and security analysis.
planner
Creates implementation plans from context and requirements.
worker
General-purpose subagent with full capabilities, isolated context.