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/plangit 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.00010 | $0.04000 |
| Opus 5 | $0.00005 | $0.02000 |
| Sonnet 5 | $0.00002 | $0.00800 |
| Haiku 4.5 | $0.00001 | $0.00400 |
Grade A, and why
plan 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 — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Analysis Workflow
Analyze the PRD at $ARGUMENTS and create a structured implementation plan.
Argument Parsing
Parse $ARGUMENTS to extract:
- Mode:
--headless(autonomous, no prompts) or--review(review existing plan) or default (interactive) - PRD Path: Remaining argument after flags
Example arguments:
docs/prd.md→ mode=interactive, path=docs/prd.md--headless docs/prd.md→ mode=headless, path=docs/prd.md--review→ mode=review, path=none (loads from ohno)
Mode Routing
- If
--review: skip to "## Plan Review Session" section below - If
--headless: run Steps 1-7 with all prompts auto-decided (see Headless Behavior below) - Otherwise: run Steps 1-7 interactively (current behavior)
Headless Behavior
When --headless is active, suppress ALL user-facing prompts and auto-decide:
Decision Logging
Every auto-decision MUST be logged via ohno:
mcp__ohno__add_task_activity:
task_id: <relevant_task_or_epic_id>
type: "decision"
description: "CATEGORY: rationale"
Categories: SPIKE, DESIGN, SPLIT, MERGE, DEPENDENCY, PRIORITY, SCOPE
Examples:
"SPIKE: Created spike for Redis session storage — PRD says 'fast sessions' but doesn't specify technology""DESIGN: Added 3 design-first tasks — PRD mentions wireframes, user flows, responsive layout (2+ UI/UX categories detected)""DEPENDENCY: Made payment integration depend on auth spike — need session approach first"
Cross-cutting decisions (SPLIT, SCOPE, MERGE) go on the epic. Task-specific decisions go on the task.
Auto-Decisions
| Interactive Prompt | Headless Auto-Decision | Decision Category |
|---|---|---|
| Design plugin: "Create design tasks now?" | Yes (create design tasks + dependencies) | DESIGN |
| Design plugin: "Continue without design plugin?" | Yes (continue without) | — (no decision needed) |
| Spike opportunity detected | Create the spike task | SPIKE |
| Feature split into multiple stories | Split and log rationale | SPLIT |
| Non-obvious dependency added | Add dependency and log | DEPENDENCY |
| Priority differs from PRD ordering | Assign and log rationale | PRIORITY |
| PRD item excluded as out-of-scope | Exclude and log rationale | SCOPE |
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 · 459 lines · 10 tokens per session scan A 9f758e325967
plan is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 4,000 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.