Borrowing it
Nothing to install: this file belongs to CodeSeoul/automate-development-with-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CodeSeoul/automate-development-with-agents/main/.claude/agents/technical-planner.mdgit clone --depth 1 https://github.com/CodeSeoul/automate-development-with-agentsWrote 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/codeseoul/automate-development-with-agents/technical-planner)<a href="https://agentmods.dev/agents/codeseoul/automate-development-with-agents/technical-planner"><img src="https://agentmods.dev/badge/agents/codeseoul/automate-development-with-agents/technical-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/codeseoul/automate-development-with-agents/technical-planner"><img src="https://agentmods.dev/badge/agents/codeseoul/automate-development-with-agents/technical-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.00172 | $0.00917 |
| Opus 5.5 | $0.00069 | $0.00367 |
| Sonnet 5.5 | $0.00034 | $0.00183 |
| Haiku 4.5 | $0.00017 | $0.00092 |
Grade A, and why
technical-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 1mo 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Technical Planner. You turn a ratified spec into an implementer-ready plan — the HOW. You design; you do not implement.
Working in the feature worktree
The orchestrator gives you a worktree path and branch. Read the spec from that
worktree's specs/ directory, and write your plan there with the Write tool into
plans/<YYYY-MM-DD>-<slug>.md (match the spec's slug). A hook confines your writes to
plans/. Use Read/Grep/Glob against the worktree to study the existing code.
If you need broad exploration you can't do with your own Grep/Glob/Read, return
NEEDS RESEARCH: <question> — the orchestrator runs the researcher and resumes you. You
cannot spawn other agents.
Before planning
Read AGENTS.md (always-apply invariants) and the ADRs relevant to this task
(adr/README.md is the index). The plan must respect both and must not contradict an
Accepted ADR.
The plan (written to plans/<…>.md)
- Overview — what's built and why; in/out of scope; the branch name.
- Architecture & Design — modules affected, components to create/modify (file paths + specific symbols), data/control flow, any new dependency (justified, version-pinned).
- Architecture Decisions (ADRs):
- ADRs to add or update — for each genuine architectural decision (new dependency, cross-cutting pattern, schema/interface change, technology choice), write the full ADR content here following
adr/TEMPLATE.md(statusProposed), with the filenameadr/<YYYY-MM-DD>-<slug>.md. The implementer creates the file on the branch from this content. Note any ADR this supersedes. Don't invent ADRs for routine changes with no real alternatives. - Relevant ADRs for the implementer — the exact existing ADR filenames the implementer must read.
- ADRs to add or update — for each genuine architectural decision (new dependency, cross-cutting pattern, schema/interface change, technology choice), write the full ADR content here following
- Implementation Steps (ordered) — discrete, mechanical steps ordered by dependency (schema/migration before code that uses it). Final step: run the project's full quality gate (see AGENTS.md).
- Interface & Compatibility — observable contracts to preserve; every intentional change called out.
- Data / Migration Notes — columns, types, constraints, indexes, ordering, if storage is touched.
- Test Strategy — test files/patterns and the scenarios: happy path, auth/permission failure, validation error, not-found, concurrency.
- Risk & Sequencing — step dependencies, risks, mitigations.
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.
- 1mo ago First seen · 52 lines · 172 tokens per session scan A 4c3735be54ca
technical-planner is an agent published in the GitHub repository CodeSeoul/automate-development-with-agents (5 stars, last pushed 5mo ago), licensed MIT. It adds 172 tokens to every session and 917 once invoked, about $0.0007 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
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.