Borrowing it
Nothing to install: this file belongs to EEstevanell/codex-planning-kit. 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/EEstevanell/codex-planning-kit/main/.codex/skills/implement-issue-execplan/SKILL.mdgit clone --depth 1 https://github.com/EEstevanell/codex-planning-kitWrote 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/eestevanell/codex-planning-kit/implement-issue-execplan)<a href="https://agentmods.dev/skills/eestevanell/codex-planning-kit/implement-issue-execplan"><img src="https://agentmods.dev/badge/skills/eestevanell/codex-planning-kit/implement-issue-execplan/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/eestevanell/codex-planning-kit/implement-issue-execplan"><img src="https://agentmods.dev/badge/skills/eestevanell/codex-planning-kit/implement-issue-execplan.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.00068 | $0.00618 |
| Opus 5.5 | $0.00027 | $0.00247 |
| Sonnet 5.5 | $0.00014 | $0.00124 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
implement-issue-execplan 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 2mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Issue + ExecPlan
Overview
Implement changes driven by an issue card and ExecPlan while keeping the plan updated, traceable, and aligned to AGENTS.md, PLANS.md, and any repo docs the issue references. We do not want over engineering, nor cluttering too much. We must follow the DRY principle and the best practices and guidelines.
Inputs
- ISSUE_PATH: Path to the issue card file (required).
- EXECPLAN_PATH: Path to the ExecPlan file (required).
Workflow (follow in order)
1) Inputs and preflight reading
- Require ISSUE_PATH and EXECPLAN_PATH; ask for them if missing or ambiguous.
- Read these files end-to-end, in order:
AGENTS.md,PLANS.md, any repo docs referenced by the issue card, ISSUE_PATH, EXECPLAN_PATH. - Treat referenced repo docs as authoritative for their scope; record conflicts in the ExecPlan Decision Log.
2) ExecPlan reconciliation (before code)
- Validate the ExecPlan includes every section required by
PLANS.md. - Ensure each plan step is deterministic, file-scoped, and includes validation criteria.
- Update the ExecPlan in place if anything is missing or stale; include assumptions, risks, and dependencies.
3) Implementation loop (repeat per step)
- Execute only one planned step (or a tight subset) at a time.
- Keep diffs minimal, follow existing patterns, and avoid new abstractions unless they clearly reduce duplication.
- Update the ExecPlan after each step.
- Record progress: what changed and which steps are complete/in progress.
- Record the decision log: why choices were made, with references to AGENTS/PLANS/Dingus docs or issue text.
- Record validation: how to verify the step and expected outcome.
4) Validation and closure
- Run every validation listed in the ExecPlan.
- Add missing validations discovered during implementation and record results.
- Ensure acceptance criteria from the issue are explicitly satisfied and verifiable.
Output requirements
- Summarize what changed (short).
- List exact file paths touched and why.
- Provide validation evidence (commands run plus result or expected output).
- Confirm the ExecPlan is complete and up to date.
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.
- 2mo ago First seen · 58 lines · 68 tokens per session scan A b8beefd1b4a0
implement-issue-execplan is a skill published in the GitHub repository EEstevanell/codex-planning-kit (2 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 618 once invoked, about $0.0003 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…