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/cpliakas/claude-code-engineering-leaders/plan-implementationnpx skills add cpliakas/claude-code-engineering-leaders --skill plan-implementationgit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWhat 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.00088 | $0.03455 |
| Opus 5 | $0.00044 | $0.01728 |
| Sonnet 5 | $0.00018 | $0.00691 |
| Haiku 4.5 | $0.00009 | $0.00346 |
Grade A, and why
plan-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 3d 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Implementation
Drive the Tech Lead's two-phase implementation planning protocol end-to-end, producing a fully synthesized implementation plan without requiring manual orchestration of the two phases.
Dependencies
This skill depends on the Parseable Phase 1 Output Contract defined in
agents/tech-lead.md (see the "Parseable Phase 1 Output Contract" subsection
under Implementation Planning). If the Tech Lead's Phase 1 output format
changes, this skill's parsing logic must be updated to match. Conversely, if
this skill's parsing logic changes in a way that requires new contract fields or
relaxes existing constraints, the contract in agents/tech-lead.md must also be
updated to reflect the new expected format.
Accepted Input Forms
$ARGUMENTS accepts three forms:
- Inline story body: paste the full story or issue description directly as the argument. The skill uses it verbatim.
- File path: a path to a markdown file containing the story or issue body
(e.g.,
./stories/auth-feature.mdor/path/to/story.md). The skill reads the file and uses its contents. - Issue reference: an issue identifier (e.g.,
ENG-123,#42,beads-456). The skill attempts to resolve it via the configured issue tracker CLI (e.g.,bd show <id>,gh issue view <id>). If no CLI is available or the reference cannot be resolved, the skill prompts for the story body before proceeding.
Step 1: Resolve Input
If $ARGUMENTS is empty, prompt the user:
Please provide the story or issue to plan. You can paste the story body directly, provide a file path (e.g.,
./story.md), or provide an issue reference (e.g.,ENG-123). Do not proceed until a story or issue is provided.
Do not guess. Do not continue with a placeholder or fabricated story.
Once $ARGUMENTS is provided or confirmed:
- If it looks like a file path (starts with
/,./, or../): use the Read tool to load the file. If the file does not exist, report the error and prompt for the story body directly. - If it looks like an issue reference (the entire trimmed value matches patterns
like
[A-Z]+-\d+,#\d+, orbeads-\d+): attempt to resolve via a configured CLI. Trybd show $ARGUMENTSfirst; if unavailable, trygh issue view $ARGUMENTS. If the command exits non-zero, is not found, or returns empty output, surface the failure and prompt for the story body directly:[INPUT ERROR] Could not resolve `[issue reference]` (tried: `[command]`). Please paste the story body directly. - Otherwise: treat
$ARGUMENTSas the inline story body.
What ships with it
7 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.
- test-fixtures/README.md 1.9 KB
- test-fixtures/story-all-specialists-missing.md 1.5 KB
- test-fixtures/story-happy-path.md 2.2 KB
- test-fixtures/story-no-specialists.md 797 B
- test-fixtures/story-parse-failure.md 1.3 KB
- test-fixtures/story-slug-missing.md 1.4 KB
- test-fixtures/story-specialist-empty.md 1.4 KB
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.
- 3d ago First seen · 378 lines · 88 tokens per session scan A 33034d4cfd39
plan-implementation is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 11d ago), licensed MIT. It adds 88 tokens to every session and 3,455 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…