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 TheSyart/emperor-agent --skill planning-implementationgit clone --depth 1 https://github.com/TheSyart/emperor-agentWrote 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/thesyart/emperor-agent/planning-implementation)<a href="https://agentmods.dev/skills/thesyart/emperor-agent/planning-implementation"><img src="https://agentmods.dev/badge/skills/thesyart/emperor-agent/planning-implementation.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 165 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00089 | $0.02912 |
| Opus 5 | $0.00044 | $0.01456 |
| Sonnet 5 | $0.00018 | $0.00582 |
| Haiku 4.5 | $0.00009 | $0.00291 |
Grade A, and why
planning-implementation 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 8d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Implementation
Overview
Write comprehensive implementation planning documents — not just task lists. Each plan produces a self-contained, reviewable document that a skilled engineer with zero domain context can execute. Plans include per-task detailed design, quantified acceptance criteria, dependency topology, risk assessment, and progress tracking.
Announce at start: "Using planning-implementation skill to create the implementation plan."
Save plans to: docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md
The Rule
Plan before code. Always. Even when the path seems obvious, writing it down surfaces hidden complexity, missing dependencies, and ambiguous requirements before they waste implementation time.
digraph planning_flow {
rankdir=TB;
"Requirements / Spec" [shape=doublecircle];
"Phase 0: Setup" [shape=box];
"Phase 1: Analyze" [shape=box];
"Phase 2: Design & Decompose" [shape=box];
"Phase 3: Verify & Output" [shape=box];
"Plan Document" [shape=doublecircle];
"Requirements / Spec" -> "Phase 0: Setup";
"Phase 0: Setup" -> "Phase 1: Analyze";
"Phase 1: Analyze" -> "Phase 2: Design & Decompose";
"Phase 2: Design & Decompose" -> "Phase 3: Verify & Output";
"Phase 3: Verify & Output" -> "Plan Document";
}
Quality Standard
The plan document must meet this bar: an engineer who has never seen this codebase, given only this document, can implement every task correctly and verify their own work. If they'd need to ask you a question, the plan has a gap.
Red Flags
These thoughts mean STOP — you're producing an insufficient plan:
| Thought | Reality |
|---|---|
| "This is too simple to need detailed design" | Simple things become complex with no fallback. Write the design. |
| "Passing tests is the acceptance criteria" | That's not AC. Write a binary checklist. |
| "I'll figure out dependencies later" | Dependencies determine execution order. Draw the topology now. |
| "One sentence for design is enough" | One sentence cannot guide implementation. Write data models, algorithms, invariants. |
| "Edge cases will be handled in code" | Edge cases not listed now will be missed during implementation. |
| "Risks don't need mitigation strategies" | Identifying without mitigating = not identifying. Every risk needs a response. |
| "Too many source files to list them all" | Then it's not a complete plan. Trace every file. |
| "Estimates are always wrong anyway" | A wrong estimate beats no estimate. Estimate by order of magnitude. |
| "I'll think about tests later" | Tests are a design tool now. List test cases before writing tasks. |
| "Skipping RED confirmation saves time" | Skipping RED = tests are invalid. Fail first, then pass. |
What ships with it
2 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.
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.
- 8d ago First seen · 253 lines · 0 tokens per session scan A cb54f80bd41a
planning-implementation is a skill published in the GitHub repository TheSyart/emperor-agent (183 stars, last pushed 26d ago), licensed MIT. It adds 89 tokens to every session and 2,912 once invoked, about $0.0004 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 skills, from other repositories
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
image-generation
Generate or edit images from text prompts. Use when the user asks to create, draw, design, or edit an image, illustration, photo, icon, poster, or any visual content.
knowledge-wiki
Manage the personal knowledge wiki. Use when the user shares articles, documents, or asks to organize knowledge; when a conversation produces insights worth preserving as structured knowledge; or when the user asks about the knowledge base.
smart-docs
AI-powered comprehensive codebase documentation generator. Analyzes project structure, identifies architecture patterns, creates C4 model diagrams, and generates professional technical documentation. Use when users need to document codebases, understand software architecture, create technical specs, or generate…
ai-context
Project knowledge base for coding agents. Activate when: (1) starting a new session in this project, (2) encountering unfamiliar code patterns or architecture decisions, (3) user asks about project design or rationale, (4) before making significant structural changes. Contains tiered knowledge from stable design…
deepwiki-rs
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming…