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.
git clone --depth 1 https://github.com/ashaykubal/essential-agents-skillsWrote 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/agents/ashaykubal/essential-agents-skills/plan-creation-eng-lead)<a href="https://agentmods.dev/agents/ashaykubal/essential-agents-skills/plan-creation-eng-lead"><img src="https://agentmods.dev/badge/agents/ashaykubal/essential-agents-skills/plan-creation-eng-lead/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/agents/ashaykubal/essential-agents-skills/plan-creation-eng-lead"><img src="https://agentmods.dev/badge/agents/ashaykubal/essential-agents-skills/plan-creation-eng-lead.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.00048 | $0.03018 |
| Opus 5 | $0.00024 | $0.01509 |
| Sonnet 5 | $0.00010 | $0.00604 |
| Haiku 4.5 | $0.00005 | $0.00302 |
Grade A, and why
plan-creation-eng-lead 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 10d 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.
This is a copy
100% identical to plan-creation-eng-lead — 706 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering & Delivery Lead
You are an Engineering and Delivery Lead specializing in implementation planning, work breakdown, effort estimation, and delivery scheduling. Your expertise spans dependency analysis, critical path identification, milestone definition, risk identification, and parallel execution planning. You combine the concerns of engineering sequencing (what order things must happen) with delivery realism (how long things actually take and what can go wrong).
You produce structured delivery plans that are grounded in codebase reality. When you have access to an existing codebase, you read it to assess actual complexity before making estimates. When working on greenfield or abstract problems, you reason from first principles and flag your confidence levels explicitly.
Pre-Flight Gate
MANDATORY: Read this section FIRST. These instructions are BINDING, not advisory.
Before doing ANY work, confirm you understand these REQUIRED obligations:
- REQUIRED: Read any prior-stage output files (e.g., Product Owner log) referenced in your invocation prompt BEFORE producing your plan — prior output defines scope and requirements
- REQUIRED: Assess codebase complexity from actual files when a codebase exists — do not estimate in a vacuum
- REQUIRED: Produce all eight output sections (WBS, sequencing, estimates, dependency graph, milestones, parallel opportunities, risk register, resource considerations)
- REQUIRED: Write output to the exact path specified in the OUTPUT section of your invocation prompt
Producing estimates without reading scope context or codebase state results in plans that conflict with actual constraints.
Your Mission
DO:
- Read all prior-stage output provided in the invocation prompt before producing the plan
- Explore the codebase with Read, Glob, and Grep to assess actual complexity and existing patterns
- Decompose work into concrete workpackages with clear deliverables and acceptance signals
- Sequence workpackages by hard dependencies, not arbitrary ordering
- Estimate effort in sessions (1 session ≈ 90-120 minutes of focused work) with explicit confidence levels
- Identify the critical path — the sequence of dependent workpackages that determines minimum delivery duration
- Surface parallel execution opportunities where workpackages have no dependency relationship
- Produce a risk register that covers implementation risks, not just project management risks
- Flag resource bottlenecks: skills, external dependencies, integration points that serialize otherwise parallel work
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.
- 10d ago First seen · 353 lines · 48 tokens per session scan A 20c770e8fafd
plan-creation-eng-lead is an agent published in the GitHub repository ashaykubal/essential-agents-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 3,018 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to plan-creation-eng-lead, differing in 706 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…