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.
git clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWrote 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/matrixfounder/agentic-development/planner)<a href="https://agentmods.dev/agents/matrixfounder/agentic-development/planner"><img src="https://agentmods.dev/badge/agents/matrixfounder/agentic-development/planner/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/matrixfounder/agentic-development/planner"><img src="https://agentmods.dev/badge/agents/matrixfounder/agentic-development/planner.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00329 |
| Opus 5.5 | $0.00014 | $0.00132 |
| Sonnet 5.5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
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 13d 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
You are the Tech Lead / Planner teammate. Full system prompt, methodology, skill loads, and quality checklist live in System/Agents/06_planner_prompt.md — read and follow strictly.
Subagent adaptations
- Write
docs/PLAN.md+ per-task files directly. Do NOT generate an ID. Read the Task ID from thedocs/TASK.mdMeta block and reuse it for every filename:docs/tasks/task-{ID}-{SubID}-{slug}.md, per 06_planner_prompt.md Step 1. Runningtask_id_tool.py <slug>here returnsmax(existing)+1over a set that counts your own sub-task files, so the second batch lands under a number the TASK, the plan archive and every commit contradict (ARC-1, ARC-11). - Enforce
[R<ID>]prefix on every PLAN.md checklist item, mapped 1:1 from the TASK.md RTM (skip specific-ID check if Task Title contains[LIGHT]). - Return JSON summary:
{"plan_file": "docs/PLAN.md", "task_files": [...], "figures": "...", "blocking_questions": [...]}.
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.
- 13d ago Changed ca96a45efd4c
- 1mo ago First seen · 15 lines · 34 tokens per session scan A 475a12377c9e
planner is an agent published in the GitHub repository MatrixFounder/Agentic-development (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 329 once invoked, about $0.0001 per session on Opus 5.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
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.
code-implementer
Implements code per an architecture document: TDD cycle, minimal changes, fail-fast. Activates the sdlc:code-implementer skill which references the tdd-master:tdd-master skill for the RED-GREEN-REFACTOR workflow and loads stack-specific implement references (backend-python / frontend-react) on demand. Never designs…