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/revisegit 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/commands/srstomp/pokayokay/revise)<a href="https://agentmods.dev/commands/srstomp/pokayokay/revise"><img src="https://agentmods.dev/badge/commands/srstomp/pokayokay/revise.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.00010 | $0.01946 |
| Opus 5 | $0.00005 | $0.00973 |
| Sonnet 5 | $0.00002 | $0.00389 |
| Haiku 4.5 | $0.00001 | $0.00195 |
Grade A, and why
revise 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Revision Workflow
Revise the current plan with impact analysis before making changes.
Mode: $ARGUMENTS (default: explore)
Mode Detection
Parse $ARGUMENTS:
--directflag → Direct mode (you know what to change)- No flag → Explore mode (guided discovery)
- Specific statement without flag → Auto-detect direct mode
If user says something specific like "I want to remove feature X" without --direct, treat as direct mode.
Session Start
1. Check for Existing Plan
Use ohno MCP get_project_status to check:
- Total task count
- Task breakdown by status
If no tasks exist:
No plan found. Use `/pokayokay:plan` first to create tasks.
Exit early.
2. Load Full Context
Use ohno MCP tools:
get_tasks(fields: "standard") → All tasks with descriptions
get_project_status() → Summary statistics
Build mental model:
- Epics and their stories
- Task dependencies
- Current progress (what's done, in progress, blocked)
3. Report Current State
## Current Plan
**Status**: X tasks total (Y done, Z in progress)
**Epics**:
- [Epic 1]: N tasks
- [Epic 2]: N tasks
**In Progress**: [list any active work]
**Blocked**: [list any blockers]
Explore Mode
When user is unsure what needs to change.
1. Open with Discovery Question
Ask ONE question to start:
Looking at your current plan, what's bothering you?
1. **Technical approach** - The tickets assume an approach I disagree with
2. **Scope** - Features need to be added, removed, or changed
3. **Priority/ordering** - Dependencies or priorities are wrong
4. **Something else** - Let me explain...
2. Drill Down with Follow-up Questions
Based on answer, ask targeted follow-ups:
- One question at a time
- Multiple choice when possible
- Surface connections: "If we change X, ticket Y depends on it"
3. Propose 2-3 Approaches
Once you understand the concern:
## Approaches
**Option A (Recommended)**: [description]
- Pros: [list]
- Cons: [list]
- Impact: [N tasks affected]
**Option B**: [description]
- Pros: [list]
- Cons: [list]
- Impact: [N tasks affected]
Which approach would you like to explore?
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 · 338 lines · 10 tokens per session scan A 31be51b61c0f
revise is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 1,946 once invoked, about $0.0001 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.