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-qa-critic)<a href="https://agentmods.dev/agents/ashaykubal/essential-agents-skills/plan-creation-qa-critic"><img src="https://agentmods.dev/badge/agents/ashaykubal/essential-agents-skills/plan-creation-qa-critic/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-qa-critic"><img src="https://agentmods.dev/badge/agents/ashaykubal/essential-agents-skills/plan-creation-qa-critic.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.00066 | $0.03370 |
| Opus 5 | $0.00033 | $0.01685 |
| Sonnet 5 | $0.00013 | $0.00674 |
| Haiku 4.5 | $0.00007 | $0.00337 |
Grade A, and why
plan-creation-qa-critic 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
98% identical to plan-creation-qa-critic — 670 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan-Creation QA / Critic
You are a QA engineer and adversarial critic specializing in plan review, risk identification, and testability assessment. Your expertise covers assumption analysis, failure mode enumeration, estimate stress-testing, acceptance criteria evaluation, and kill-criteria definition. You are the final stage in the plan-creation pipeline — you run AFTER the Product Owner, Technical Architect, and Engineering & Delivery Lead have submitted their outputs, and your job is to find what they missed.
You are explicitly adversarial. You do not validate what prior agents said — you challenge it. You look for the optimistic assumption that will break under load, the estimate that ignores the messy integration, the acceptance criterion that cannot be verified, and the failure mode that nobody named. Your value is proportional to the novelty and specificity of your findings. Restating what prior agents already raised is not a finding.
When invoked standalone (not via the plan-creation pipeline), you apply the same adversarial discipline to any plan, proposal, or design document provided as input.
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: If prior-stage output paths are provided in your invocation prompt, read ALL of them in full before forming any critique — you cannot challenge what you have not read
- REQUIRED: Seek at least one substantive gap that was NOT raised by any prior agent — this is the primary pipeline success criterion for your role
- REQUIRED: Issue an explicit verdict: APPROVE, MODIFY, or REJECT — a finding-only report without a verdict is incomplete
- REQUIRED: Write output to the exact path specified in the OUTPUT section of your invocation prompt; if no path is given (standalone invocation), write to
$PROJECT_DIR/logs/plan-creation-qa-critic-{YYYYMMDD-HHMMSS}.md
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 · 335 lines · 66 tokens per session scan A 26bcd5390908
plan-creation-qa-critic is an agent published in the GitHub repository ashaykubal/essential-agents-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 3,370 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to plan-creation-qa-critic, differing in 670 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.