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 skills add pantheon-org/tekhne --skill implementation-plannergit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/skills/pantheon-org/tekhne/implementation-planner)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/implementation-planner"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/implementation-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/skills/pantheon-org/tekhne/implementation-planner"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/implementation-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.00138 | $0.04344 |
| Opus 5 | $0.00069 | $0.02172 |
| Sonnet 5 | $0.00028 | $0.00869 |
| Haiku 4.5 | $0.00014 | $0.00434 |
Grade B, and why
implementation-planner scanned grade B with 1 finding 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 9d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
run any scripts, do not create any files. Instead, message the user with the How it starts
The opening of the file, as written. The whole thing — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Planner
Mental model
An implementation plan is a navigable contract between an agent and a codebase. Each file answers a single question: "What do I need to do next, how do I do it, and how do I prove it is done?"
Two failure modes to avoid:
- The monolith — one giant plan.md nobody reads because everything is in one file
- The skeleton — directories with empty READMEs that give no useful signal
The sweet spot is a tree where every node either navigates (README) or implements (task file), and every leaf has a runnable verification command.
Quick Start
Mode 1 — Create a new plan from a PRD:
sh scripts/new-plan.sh url-shortener-service
sh scripts/new-phase.sh url-shortener-service 01 workspace-bootstrap
sh scripts/new-task.sh url-shortener-service 01 01 initialise-npm-package
sh scripts/validate-plan.sh url-shortener-service
Mode 2 — Split a monolithic document:
# 1. Create hierarchy manually (steps below) or from JSON:
sh scripts/generate-structure.sh --plan plan.json
# 2. Validate before removing source
sh scripts/validate-structure.sh docs/refactoring/phases
When to use each mode
| Signal | Mode |
|---|---|
| User provides a PRD, spec, or requirements description | Mode 1 |
| User provides a single large planning document to split | Mode 2 |
| User provides flat phase files to reorganise | Mode 2 |
| User says "add a phase" to an existing plan | Mode 1 (additive) |
| User says "split", "organise", "refactor this plan" | Mode 2 |
Trigger phrases
Creating a new plan:
- "create an implementation plan"
- "plan this out in phases"
- "break this PRD into tasks"
- "generate a phased plan"
- "write a detailed implementation plan"
- "create tasks from this spec"
- "decompose this into phases and tasks"
- "create a project plan / roadmap"
- "break down tasks" / "task breakdown"
- "sprint planning"
Restructuring an existing plan:
- "split this plan"
- "organize phases"
- "break down implementation docs"
- "create task hierarchy"
- "refactor this planning doc"
- "split this into separate files"
What ships with it
37 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .audits/2026-03-10/analysis.md 1.1 KB
- .audits/2026-03-10/audit.json 459 B
- .audits/2026-03-10/remediation-plan.md 3.6 KB
- .audits/2026-03-11/analysis.md 1.1 KB
- .audits/2026-03-11/audit.json 460 B
- .audits/2026-03-11/remediation-plan.md 2.3 KB
- .audits/2026-04-06/analysis.md 1.2 KB
- .audits/2026-04-06/audit.json 514 B
- .audits/2026-04-06/remediation-plan.md 2.4 KB
- .audits/latest 10 B
- evals/scenario-01.md 5.1 KB
- evals/scenario-02.md 4.7 KB
- evals/scenario-03.md 5.9 KB
- evals/scenario-04.md 5.4 KB
- evals/scenario-05.md 4.8 KB
- references/anti-patterns.md 8.5 KB
- references/example-transformation.md 3.7 KB
- references/mode2-advanced.md 3.3 KB
- references/schemas/phase.schema.json 1.1 KB
- references/schemas/plan.schema.json 1.1 KB
- references/schemas/readme-file.schema.json 2.2 KB
- references/schemas/step-file.schema.json 6.1 KB
- references/schemas/task.schema.json 1.6 KB
- references/templates/group-readme.yaml 1.1 KB
- references/templates/intermediate-readme.yaml 643 B
- references/templates/phase-readme.yaml 1.1 KB
- references/templates/phase.yaml 2.4 KB
- references/templates/plan.yaml 1.6 KB
- references/templates/step-file.yaml 1.3 KB
- references/templates/task.yaml 2.5 KB
- references/worked-examples.md 3.1 KB
- scripts/generate-structure.sh 21 KB runs code
- scripts/new-phase.sh 1.0 KB runs code
- scripts/new-plan.sh 633 B runs code
- scripts/new-task.sh 1.6 KB runs code
- scripts/validate-plan.sh 4.5 KB runs code
- scripts/validate-structure.sh 14 KB runs code
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.
- 9d ago First seen · 464 lines · 138 tokens per session scan B f3e782c076e5
implementation-planner is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 138 tokens to every session and 4,344 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
atlas-obscura
Search Atlas Obscura for weird, wonderful, and hidden gem places near any destination. Find the interesting stuff, not boring plaques. Search by coordinates, get full details with descriptions and images.
agent-code-generator
Generates Agent definitions (.md files) based on user intent and standard templates.
cf-validate
A validator for 1C configuration source files. It checks the XML structure and the files and objects that make up a 1C business-application configuration.