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 skills/soden46/engineer-flow/planning-executionnpx skills add soden46/engineer-flow --skill planning-executiongit clone --depth 1 https://github.com/soden46/engineer-flowWrote 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/soden46/engineer-flow/planning-execution)<a href="https://agentmods.dev/skills/soden46/engineer-flow/planning-execution"><img src="https://agentmods.dev/badge/skills/soden46/engineer-flow/planning-execution.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 | $0.00023 | $0.00303 |
| Opus 5 | $0.00012 | $0.00151 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
planning-execution 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 4d 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
planning-execution
Use this skill when work should be planned before implementation.
Principles
A useful engineering plan identifies:
- objective
- affected components
- ordered implementation steps
- dependencies
- risks
- verification
- rollout or rollback when relevant
Prefer concrete actions over vague statements.
Separate required work from optional improvements.
Keep scope aligned with the requested outcome.
For risky changes identify checkpoints where correctness can be verified before continuing.
Plans should be executable by another engineer without requiring hidden assumptions.
Adaptation
Use project evidence to determine the actual language, framework, runtime, and existing conventions.
When stack-specific implementation guidance is needed, prefer project evidence, native framework or language mechanisms, and relevant user-installed specialist skills. Technology-specific guidance must not redefine or weaken the core engineering requirement.
Absorbed Legacy Capability: planning
The following framework-agnostic knowledge was preserved from the previous Engineer Flow capability during consolidation.
Planning
Plan enough to move safely.
- Identify objective, constraints, affected surfaces, and verification.
- Sequence work in small reversible steps.
- Keep at most one active implementation thread.
- Re-plan when current code disproves assumptions.
- Stop planning once execution is clear.
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.
- 4d ago First seen · 57 lines · 23 tokens per session scan A b4f901ed46e3
planning-execution is a skill published in the GitHub repository soden46/engineer-flow (3 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 303 once invoked, about $0.0001 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-31.
Other skills, from other repositories
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
clarify
Adaptive requirements clarification with auto-depth routing. Shallow (Q&A) for simple tasks, Deep (exploration + DRAFT + PLAN) for complex ones. Escalates automatically when ambiguity persists.
auditing-aws-s3-bucket-permissions
Systematically audit AWS S3 bucket permissions to identify publicly accessible buckets, overly permissive ACLs, misconfigured bucket policies, and missing encryption settings using AWS CLI, S3audit, and Prowler to enforce least-privilege data access controls.
containing-active-breach
Executes containment strategies to stop active adversary operations and prevent lateral movement during a confirmed security breach. Implements short-term and long-term containment using network segmentation, endpoint isolation, credential revocation, and access control modifications. Activates for requests involving…