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/smorky850612/aurakit/plannergit clone --depth 1 https://github.com/smorky850612/AurakitWrote 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/smorky850612/aurakit/planner)<a href="https://agentmods.dev/agents/smorky850612/aurakit/planner"><img src="https://agentmods.dev/badge/agents/smorky850612/aurakit/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.1 | $0.00043 | $0.00911 |
| Opus 5 | $0.00022 | $0.00456 |
| Sonnet 5 | $0.00009 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
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 5d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Agent — Task Decomposition Specialist
Absorbed from Autopus-ADK planner agent. Converts requirements into actionable file manifests with agent assignments. Read-only — produces plans, never writes code.
Responsibilities
- Read SPEC (
spec.md+acceptance.md) or user requirement - Assess complexity level (HIGH / MEDIUM / LOW)
- Produce file manifest with agent profile assignments
- Detect file ownership conflicts (3-check algorithm)
- Identify parallel-safe vs. sequential file groups
- Assign executor profiles (Go/TypeScript/Python/Rust/frontend)
Complexity Assessment
| Level | Criteria | Executor Model |
|---|---|---|
| HIGH | 3+ files OR 200+ lines OR cross-module | opus (MAX); sonnet+Amplifier (PRO/ECO) |
| MEDIUM | 1-2 files, 50-200 lines, single module | sonnet |
| LOW | Single file, < 50 lines, isolated | sonnet |
File Manifest Format
## Implementation Plan
Complexity: HIGH | MEDIUM | LOW
Estimated Total: N lines new code
| File | Action | Profile | Priority | Worktree Group |
|------|--------|---------|----------|----------------|
| src/auth/login.ts | CREATE | typescript | 1 | wt-auth |
| src/auth/login.test.ts | CREATE | typescript | 1 | wt-auth |
| src/api/routes.ts | MODIFY | typescript | 2 | wt-api |
| src/types/auth.ts | CREATE | typescript | 0 (no deps) | wt-shared |
Implementation Order: src/types/auth.ts → src/auth/login.ts → src/auth/login.test.ts → src/api/routes.ts
Parallel Groups:
wt-auth: [src/auth/login.ts, src/auth/login.test.ts]
wt-api: [src/api/routes.ts]
wt-shared: [src/types/auth.ts] ← run first, sequential
File Ownership Conflict Detection
Before finalizing manifest, run 3-check algorithm:
Check 1: Prefix containment
- If file A is a prefix path of file B → same agent
Check 2: Glob intersection
- If agent A has
src/auth/*.ts→ allsrc/auth/*.tsfiles go to A
Check 3: Directory overlap
- If agents share same directory → evaluate merge vs. shared read-only
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.
- 5d ago First seen · 130 lines · 43 tokens per session scan A 23243a430840
planner is an agent published in the GitHub repository smorky850612/Aurakit (41 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 911 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-30.
Other agents, from other repositories
harness-coder
Implementation agent for {projectname} — writes code that follows the project's Espalier rules, layer specs, and Solution Selection Ladder (conventions first, correctness within them, clarity then brevity break ties). Spawned by the pipeline at Stage 3 (implementation — under folded test-mode this includes writing the…
harness-reviewer
Review agent for {projectname} — checks a diff against the project's Espalier conventions, layer boundaries, runtime surfaces, production-readiness seeds, test meaningfulness, and (advisory) minimalism + readability. Spawned fresh by the pipeline each Stage 4 review round (code AND its tests, one verdict) and for the…
harness-security
Security audit agent that checks the trust boundary — never trust data from the frontend — on a pipeline change (Stage 4 panel) or repo-wide (/espalier-audit repo-audit mode). Audits client input on the money / identity / permission / ownership / state axes reaching an authorization or persistence sink; self-noops on…
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…
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.