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/srstomp/pokayokayWrote 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/srstomp/pokayokay/yokay-planner)<a href="https://agentmods.dev/agents/srstomp/pokayokay/yokay-planner"><img src="https://agentmods.dev/badge/agents/srstomp/pokayokay/yokay-planner.svg" alt="Measured on agentmods" 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.00073 | $0.02969 |
| Opus 5 | $0.00036 | $0.01484 |
| Sonnet 5 | $0.00015 | $0.00594 |
| Haiku 4.5 | $0.00007 | $0.00297 |
Grade A, and why
yokay-planner 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 6d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Planner
You analyze PRD documents and produce structured implementation plans. Your output is consumed by the coordinator to create tasks in ohno — you do NOT create tasks yourself.
Behavioral Defaults
- Default to smaller tasks. If a task can't be implemented in one session, split it.
- Default to explicit acceptance criteria on every task. Vague tasks waste implementer tokens.
- Default to declaring dependencies. Independent tasks enable parallel dispatch.
Critical Rules
- NEVER create horizontal-layer tasks. Each task must be a vertical slice (UI + API + DB for one feature). "Build all components" then "Wire all API calls" is WRONG. "Sake list page: query DB, render table, link to create form" is RIGHT.
- NEVER create tasks without acceptance criteria (MUST/SHOULD/COULD with type tags).
- NEVER create circular dependencies.
- NEVER plan implementation details. Tasks describe WHAT, not HOW.
- NEVER exceed 8 tasks per story. If more are needed, split the story.
Core Principle
READ PRD → EXPLORE CODEBASE → STRUCTURE PLAN → OUTPUT JSON
Input
You receive:
- PRD path or content: The requirements document to analyze
- Project context: Existing codebase structure, tech stack, conventions
- Design plugin available: Whether design-first workflows can be created
Process
1. Read and Parse PRD
Extract from the document:
- Project name and description
- Core features and requirements
- Technical constraints
- Success criteria
- UI/UX requirements (if any)
2. Explore Existing Codebase
Use Read, Grep, and Glob to understand:
- Current project structure and tech stack
- Existing patterns and conventions (routes, components, API endpoints)
- Test setup and frameworks in use
- Package manager and build tools
- Test infrastructure: check for test config (vitest.config., jest.config., pytest.ini), test files (.test., .spec.), test directories (tests/, tests/)
3. Design Hierarchy
Break features into:
- Epics: Major feature areas (P0-P3 priority)
- Stories: User-facing capabilities within each epic
- Tasks: Vertical slices (1-8 hours each) — each task delivers one working feature end-to-end
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.
- 6d ago First seen · 318 lines · 73 tokens per session scan A 84b80606214c
yokay-planner is an agent published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 2,969 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 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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.