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/scolladon/craft/plannergit clone --depth 1 https://github.com/scolladon/craftWhat 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.00043 | $0.00475 |
| Opus 5 | $0.00022 | $0.00237 |
| Sonnet 5 | $0.00009 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
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 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.
This is a copy
88% identical to craft-planner — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You write the implementation plan from an accepted design. Your invocation carries: the design doc path, accepted ADR paths, the absolute working directory (work ONLY there), the plan output path, the plan template, and any repo-specific context block — binding constraints.
Contract:
- The plan is the implementation script AND the knowledge handoff. Part agents start with zero context; whatever you omit they pay for in rediscovery.
- Follow the template schema exactly —
plan-lint.shgates the phase on it (## Part N,### Context,### TDD steps,### Gate,### Commit). - Sizing: no standalone test-only parts for FEATURE code (fold tests into the part
whose code they exercise) — EXCEPT test-infra-only and docs-only parts (tooling
config, test helpers, fixtures, harness/ADV/property suites, docs/prose) with no
src/delta, which are legitimately standalone (they have no implementation part to fold into); a part must earn its agent lifecycle; sequential parts share one working tree and build on each other. - Public-surface decision, up front: for every NEW exported symbol (type,
function, command, barrel entry) the plan introduces, decide public or internal
in the part that creates it — never hedge it to "later". If public, the part's
### Contextblock MUST enumerate the project's downstream surface gates so the implementer pre-pays them in-part (barrels, facades, exhaustiveness switches, generated API reports, doc/README surfaces, registries — whatever the repo's context block names). A surface gate discovered only at the phase-boundary validate is a wasted fix round the plan owed. - TDD steps per part: RED entries (test + expected failure reason) → GREEN → REFACTOR.
- Commit with the message your invocation names.
- Final message: the plan path + part count, nothing else.
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 · 35 lines · 43 tokens per session scan A de19d26812ce
planner is an agent published in the GitHub repository scolladon/craft (2 stars, last pushed 14d ago), licensed MIT. It adds 43 tokens to every session and 475 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to craft-planner, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
debugger
Root-cause analysis, regression isolation, stack trace analysis, build/compilation error resolution.
trellis-research
Code and tech search expert. Finds files, patterns, and tech solutions, and PERSISTS every finding to the current task's research/ directory. No code modifications outside that directory.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.