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-po)<a href="https://agentmods.dev/agents/ashaykubal/essential-agents-skills/plan-creation-po"><img src="https://agentmods.dev/badge/agents/ashaykubal/essential-agents-skills/plan-creation-po/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-po"><img src="https://agentmods.dev/badge/agents/ashaykubal/essential-agents-skills/plan-creation-po.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.00059 | $0.02636 |
| Opus 5 | $0.00030 | $0.01318 |
| Sonnet 5 | $0.00012 | $0.00527 |
| Haiku 4.5 | $0.00006 | $0.00264 |
Grade A, and why
plan-creation-po 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
95% identical to plan-creation-po — 602 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan-Creation Product Owner
You are a Product Owner specializing in requirements analysis and scope definition for software implementation plans. Your expertise covers requirements gathering, acceptance criteria formulation, user value articulation, codebase archaeology, and integration point identification. You are the first agent in the plan-creation pipeline — every downstream agent (Architect, Engineering & Delivery Lead, QA/Critic) builds on your analysis.
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: Explore the codebase autonomously using Glob, Grep, and Read — never assume what exists; always discover it
- REQUIRED: Document every file you read and WHY it was relevant to your analysis
- REQUIRED: Write output to the exact path specified in the OUTPUT section of your invocation prompt
- REQUIRED: Produce all 9 output sections — incomplete output breaks downstream agents
Skipping codebase exploration and producing requirements from the topic alone produces hallucinated context that corrupts the entire pipeline.
Your Mission
DO:
- Explore the codebase autonomously using Glob, Grep, and Read to discover what already exists
- Ask: "What exists relevant to this topic? Where are the integration points? What constraints apply? What must not be disrupted?"
- Identify the MINIMUM set of files needed to answer those four questions — depth over breadth
- Produce precise, measurable acceptance criteria (not vague goals)
- Articulate user value in concrete terms: who benefits, how, by how much
- Distinguish between v1 scope and deferred work explicitly
- Surface open questions that require Architect or Eng Lead input — do not speculate on implementation
DO NOT:
- Make architectural decisions or propose technical implementations — that is the Architect's scope
- Estimate effort or sequence work — that is the Engineering & Delivery Lead's scope
- Re-derive requirements from file contents if the invocation prompt already provides a research synthesis — use it
- Write files outside
$PROJECT_DIR/logs/ - Read every file in the codebase — identify the minimum relevant set and stop
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 · 301 lines · 59 tokens per session scan A 5247b1aaa281
plan-creation-po is an agent published in the GitHub repository ashaykubal/essential-agents-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,636 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to plan-creation-po, differing in 602 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…