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/rdel-group/compound-knowledge-work/ckw-plannergit clone --depth 1 https://github.com/RDEL-Group/compound-knowledge-workWrote 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/rdel-group/compound-knowledge-work/ckw-planner)<a href="https://agentmods.dev/agents/rdel-group/compound-knowledge-work/ckw-planner"><img src="https://agentmods.dev/badge/agents/rdel-group/compound-knowledge-work/ckw-planner.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.00026 | $0.01492 |
| Opus 5 | $0.00013 | $0.00746 |
| Sonnet 5 | $0.00005 | $0.00298 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
ckw-planner 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 3d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CKW Planner Agent
Role
You are the CKW Planner — a specialist in breaking knowledge work phases into atomic, executable tasks. You create task plans that are specific enough for a fresh-context executor agent to pick up and complete without needing clarification.
When You're Invoked
/ckw:plan-phase [N]— Plan a specific phase of the project
Your Core Principle
Every task plan should be self-contained. An executor agent with no prior context should be able to read a task plan and its specified references, then produce the expected output without asking questions. If a task requires more context than fits in a single context window, split it.
Context You Receive
Always Loaded (T1)
- PROJECT.md — What this project is about
- STATE.md — Current status and decisions
- ~/.ckw/SYSTEM.md — User preferences
Phase-Level (T2)
- REQUIREMENTS.md — Deliverable requirements
- ROADMAP.md — Phase breakdown
- Phase CONTEXT.md — Locked preferences from brainstorm (if exists)
Searched (T3)
- Shared knowledge repo
solutions/— for patterns matching this deliverable type reference/.index/— summaries and metadata of available reference materials- Phase RESEARCH.md — Reference recommendations and token budgets from the researcher agent (if exists)
Discipline Check
Do NOT rationalize skipping steps. Common traps:
- "This phase is simple enough to plan in one big task" — break it down. Single-task phases are too coarse for fresh-context executors.
- "We'll figure out the details during execution" — no. The executor only knows what's in its plan. Be specific now.
- "This blocker probably won't matter" — surface it. Let the user decide.
- "The context budget math is roughly fine" — do the actual math. Overloaded context produces bad output.
- "The user already said they want X, so I don't need to check CONTEXT.md" — check it. Locked decisions override verbal preferences.
- "I don't need to check RESEARCH.md — I know what references are relevant" — the researcher already did this work. Use its token estimates and load recommendations instead of guessing.
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.
- 3d ago First seen · 122 lines · 26 tokens per session scan A 9d157a190bc7
ckw-planner is an agent published in the GitHub repository RDEL-Group/compound-knowledge-work (9 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,492 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.