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 skills add srstomp/pokayokay --skill plan-revisiongit 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/skills/srstomp/pokayokay/plan-revision)<a href="https://agentmods.dev/skills/srstomp/pokayokay/plan-revision"><img src="https://agentmods.dev/badge/skills/srstomp/pokayokay/plan-revision.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.00039 | $0.00434 |
| Opus 5 | $0.00019 | $0.00217 |
| Sonnet 5 | $0.00008 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
plan-revision 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.
What it actually says
Plan Revision
Revise existing plans with full impact visibility.
Integrates with:
ohno— Task CRUD, dependencies, activity loggingwork-session— Works within session workflow
Quick Reference
Explore Mode
- Load context from ohno
- Ask discovery questions (one at a time)
- Surface connections and dependencies
- Propose 2-3 approaches with trade-offs
- Converge to concrete changes
- Show impact analysis
- Execute with approval
Direct Mode
- Load context from ohno
- Parse user's stated changes
- Clarify only if ambiguous
- Show impact analysis
- Execute with approval
Impact Analysis Components
| Component | Priority | When Shown |
|---|---|---|
| Ticket changes (diff table) | Primary | Always |
| Risk assessment | Primary | Always |
| Dependency graph | Secondary | Complex deps |
| Effort delta | Secondary | Significant changes |
Risk Flags
:warning: High Risk:
- Task in progress or review
- Task has logged activity
- Task has 3+ dependents
- Task on critical path
:information_source: Medium Risk:
- Dependencies need updating
- Part of partially complete epic
When NOT to Use
- Creating a new plan — Use
planningto break down PRDs into epics/stories/tasks from scratch - Working on tasks — Use
work-sessionto execute implementation; this skill only revises plans - Reviewing completed work — Use
session-reviewfor retrospective analysis
References
| Reference | Description |
|---|---|
| ohno-tools.md | ohno MCP tools used for plan revision |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 64 lines · 39 tokens per session scan A 0e7fbd9ce8d4
plan-revision is a skill published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 434 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.