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 commands/srstomp/pokayokay/auditgit clone --depth 1 https://github.com/srstomp/pokayokayWhat 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.00006 | $0.01536 |
| Opus 5 | $0.00003 | $0.00768 |
| Sonnet 5 | $0.00001 | $0.00307 |
| Haiku 4.5 | $0.00001 | $0.00154 |
Grade A, and why
audit 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 3d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Audit Workflow
Audit implementation completeness against requirements.
Feature: $ARGUMENTS (optional - audits all if not specified)
Agent Delegation
Delegate the codebase scanning to the yokay-auditor agent for isolated execution. This keeps verbose scan output separate from the main conversation.
Use the yokay-auditor agent to scan the codebase for feature implementation evidence.
Return only the summary table and critical gaps to this conversation.
The agent will:
- Detect project framework
- Scan for backend/frontend/route/navigation evidence
- Assign L0-L5 completeness levels
- Return a structured summary
After receiving the agent's summary, continue with remediation task creation below.
Steps
1. Get Task List
npx @stevestomp/ohno-cli tasks
Or use ohno MCP get_tasks.
2. Read Project Context
Read .claude/PROJECT.md for:
- Expected features
- Success criteria
- Tech stack (to know where to look)
3. Scan Codebase
For each feature/task, search for implementation evidence:
Backend indicators:
- API routes/endpoints
- Database models/migrations
- Service/controller files
Frontend indicators:
- Components/pages
- Route definitions
- Navigation links
4. Assign Completeness Levels
Dimension 1: User Accessibility (L0-L5) - Default
| Level | Name | Criteria |
|---|---|---|
| L0 | Not Started | No implementation found |
| L1 | Backend Only | API exists, no frontend |
| L2 | Frontend Exists | Component exists, not routable |
| L3 | Routable | Has route, not in navigation |
| L4 | Accessible | In navigation, missing polish |
| L5 | Complete | Fully implemented and accessible |
Dimension 2: Testing Coverage (T0-T4)
| Level | Name | Criteria |
|---|---|---|
| T0 | No Tests | No test files exist |
| T1 | Unit Only | Unit tests present, no integration |
| T2 | Integration | Unit + integration tests |
| T3 | E2E | E2E tests for critical paths |
| T4 | Full Coverage | >80% coverage, all test types |
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.
- 3d ago First seen · 208 lines · 6 tokens per session scan A 35e532e3357e
audit is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 1,536 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.