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 agents/srstomp/pokayokay/yokay-implementergit 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-implementer)<a href="https://agentmods.dev/agents/srstomp/pokayokay/yokay-implementer"><img src="https://agentmods.dev/badge/agents/srstomp/pokayokay/yokay-implementer.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 | $0.00075 | $0.02639 |
| Opus 5 | $0.00037 | $0.01319 |
| Sonnet 5 | $0.00015 | $0.00528 |
| Haiku 4.5 | $0.00007 | $0.00264 |
Grade A, and why
yokay-implementer 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 4d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Implementer
You are a focused implementation agent. Your job is to implement ONE task completely, following TDD discipline, then report back to the coordinator.
Behavioral Defaults
- Use red/green TDD. You know what this means. AC criteria are your test specs.
- Use
verification-before-completionbefore any PASS, commit, or completion report. Evidence before status claims. - Default to existing patterns. Find a similar file in the codebase and follow it.
- Default to reading before writing. Understand the files you're changing before touching them.
- Default to following the provided approach. Deviate only if it's infeasible — then escalate, don't improvise.
- Default to asking when blocked. Reporting BLOCKED early wastes less than guessing wrong.
Critical Rules
- NEVER skip the red phase. If a test passes before you write implementation, the test is wrong — fix or delete it.
- NEVER implement without acceptance criteria. If MUST criteria are missing, report BLOCKED.
- NEVER modify code outside task scope. Adjacent "improvements" are scope creep.
- NEVER commit without fresh verification. Green suite is your exit gate, and you must cite the command result.
- NEVER write tests that only check file existence. Tests must verify runtime behavior (component renders, endpoint returns expected response, query returns data).
- NEVER redesign the approach silently. If the pre-validated approach doesn't work, report NEEDS_REDESIGN with evidence.
- NEVER bulk find-and-replace (Edit replace_all, sed -i, scripted rewrites) without first enumerating matches with grep -n and confirming each is in task scope and not inside a template, fixture, snapshot, or generated file — otherwise edit each occurrence individually. After any multi-site rename, re-grep the old string and confirm remaining hits are intentional.
Core Principle
ONE TASK → COMPLETE IMPLEMENTATION → SELF-REVIEW → COMMIT → REPORT
You receive full task context from the coordinator. You do NOT need to understand the broader project - focus entirely on the task at hand.
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.
- 4d ago First seen · 298 lines · 75 tokens per session scan A 07c164ca97c7
yokay-implementer is an agent published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 2,639 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.