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/fixgit 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.00009 | $0.01373 |
| Opus 5 | $0.00005 | $0.00687 |
| Sonnet 5 | $0.00002 | $0.00275 |
| Haiku 4.5 | $0.00001 | $0.00137 |
Grade A, and why
fix 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 2d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix Workflow
Fix bug: $ARGUMENTS
Mode Selection
Check $ARGUMENTS for --thorough flag:
- Default (light pipeline): Implementer agent only, coordinator self-reviews.
--thorough: Full agent pipeline. Read and followskills/work-session/references/bug-fix-pipeline.mdinstead of this command. Stop reading here.
Bug Fix Philosophy
- Reproduce first: Confirm the bug exists and understand conditions
- Diagnose root cause: Don't just fix symptoms
- Fix with minimal change: Avoid scope creep
- Verify the fix: Confirm bug is resolved
- Add regression test: Prevent recurrence
Use systematic-debugging before edits and verification-before-completion
before reporting success. error-handling remains the implementation skill
for error-boundary, retry, API-error, and recovery-pattern changes after root
cause is known.
Steps
1. Create or Get Bug Task
If $ARGUMENTS is a task ID:
npx @stevestomp/ohno-cli get <task-id>
If $ARGUMENTS is a description:
npx @stevestomp/ohno-cli create "Bug: $ARGUMENTS" -t bug
npx @stevestomp/ohno-cli start <task-id>
2. Reproduce the Bug
Before fixing, confirm:
- Bug can be reproduced
- Reproduction steps documented
- Affected code/component identified
If cannot reproduce:
- Ask for more information
- Check if already fixed
- Document as "cannot reproduce"
3. Diagnose Root Cause
Investigate:
- Read error messages/stack traces
- Add logging to trace execution
- Check recent changes (
git log) - Review related tests
- Compare against a nearby working example
- State one hypothesis and the evidence for it before editing
Document findings:
## Root Cause
[Explanation of why the bug occurs]
4. Plan the Fix
Before coding:
- Identify files to change
- Consider side effects
- Plan regression test
5. Dispatch Implementer
Read agents/templates/implementer-prompt.md and fill these variables:
| Variable | Value |
|---|---|
{TASK_ID} |
Task ID from Step 1 |
{TASK_TITLE} |
Task title from Step 1 |
{TASK_DESCRIPTION} |
Root cause + reproduction steps + fix strategy from Steps 2-4 |
{ACCEPTANCE_CRITERIA} |
See below |
{CONTEXT} |
Bug fix context block (see below) |
{RELEVANT_SKILL} |
error-handling |
{APPROACH} |
Design review skipped — follow codebase patterns (design review does not run in the bug-fix pipeline; do NOT put the fix strategy here — it belongs in {CONTEXT}) |
{WORKING_DIRECTORY} |
Project root |
{RESUME_CONTEXT} |
Empty |
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.
- 2d ago First seen · 182 lines · 9 tokens per session scan A bae49d1f90ca
fix is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 1,373 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.