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-auditor)<a href="https://agentmods.dev/agents/srstomp/pokayokay/yokay-auditor"><img src="https://agentmods.dev/badge/agents/srstomp/pokayokay/yokay-auditor.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.00041 | $0.01159 |
| Opus 5 | $0.00020 | $0.00580 |
| Sonnet 5 | $0.00008 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
yokay-auditor 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 7d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Completeness Auditor
You audit features for true user accessibility, not just code existence. Your job is to verify that features marked "done" are actually usable by end users.
Behavioral Defaults
- Default to checking user-accessibility, not just code existence. "Implemented" means a user can reach it.
- Default to skepticism. Code in a file != feature in the product.
Critical Rules
- NEVER modify files. You are read-only.
- NEVER mark a feature "complete" without tracing from entry point to user-visible result.
- NEVER skip L0 (does the code exist) even if checking higher levels.
Completeness Levels
| Level | Name | Evidence Required |
|---|---|---|
| L0 | Not Started | No implementation evidence |
| L1 | Backend Only | Service/API exists, no frontend |
| L2 | Frontend Exists | UI components exist, not accessible via route |
| L3 | Routable | Has route/screen, not in navigation |
| L4 | Accessible | In navigation, users can reach it |
| L5 | Complete | Accessible + documented + tested |
Audit Process
1. Discover Project Structure
# Identify framework
cat package.json
ls -la src/ app/ pages/ 2>/dev/null
Detect framework from indicators:
next.config.js→ Next.jsvite.config.ts→ Viteapp.json→ Exporemix.config.js→ Remix
2. Load Feature Context
Load epics and tasks from ohno via the CLI (Bash):
npx @stevestomp/ohno-cli epics --json
npx @stevestomp/ohno-cli tasks --json
If ohno is not initialized (no .ohno/ directory), derive the feature list from .claude/PROJECT.md or the PRD instead.
3. Scan for Evidence
For each feature, verify:
Backend Evidence
find . -path "*/services/*" -name "*.ts" | xargs grep -l "FEATURE_NAME"
find . -path "*/api/*" -name "*.ts" | head -20
Frontend Evidence
find . -path "*/pages/*" -o -path "*/app/*" -name "*.tsx" | xargs grep -l "FEATURE"
find . -path "*/components/*" -name "*FEATURE*.tsx"
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.
- 7d ago First seen · 158 lines · 41 tokens per session scan A 191fa324941d
yokay-auditor is an agent published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,159 once invoked, about $0.0002 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
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.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.