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.
git clone --depth 1 https://github.com/J-Pster/Psters_AI_WorkflowWrote 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/j-pster/psters_ai_workflow/pwf-plan)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-plan"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-plan"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-plan.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.02769 |
| Opus 5 | $0.00020 | $0.01385 |
| Sonnet 5 | $0.00008 | $0.00554 |
| Haiku 4.5 | $0.00004 | $0.00277 |
Grade A, and why
pwf-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 9d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 2 — Build an Execution Plan
Note: The current year is 2026.
Use this command to convert the feature context (or brainstorm) into a phased, execution-ready plan in docs/plans/ that /pwf-work-plan can run directly.
When ambiguity materially impacts architecture/scope, run /pwf-clarify before finalizing the plan.
Apply skills/using-psters-workflow/SKILL.md at start.
⚠️ Subagent Invocation (REQUIRED)
All agents must be invoked via the Task tool (subagent_type: generalPurpose). Do not simulate or inline the agent's work. For each agent, instruct it to read its agent file and execute with the given input.
Use collision-safe agent naming in prompts:
psters-ai-workflow:research:<agent-name>psters-ai-workflow:review:<agent-name>psters-ai-workflow:workflow:<agent-name>
| Agent | File path |
|---|---|
| repo-research-analyst | agents/research/repo-research-analyst.md |
| learnings-researcher | agents/research/learnings-researcher.md |
| spec-flow-analyzer | agents/workflow/spec-flow-analyzer.md |
| migration-impact-planner | agents/research/migration-impact-planner.md |
| architecture-strategist | agents/review/architecture-strategist.md |
| security-sentinel | agents/review/security-sentinel.md |
| performance-oracle | agents/review/performance-oracle.md |
| best-practices-researcher | agents/research/best-practices-researcher.md |
| framework-docs-researcher | agents/research/framework-docs-researcher.md |
| plan-document-reviewer | agents/workflow/plan-document-reviewer.md |
0. Input
<feature_description> #$ARGUMENTS </feature_description>
If empty, ask: "What would you like to plan? Describe the feature, bug fix, or improvement."
Brainstorm check: Search docs/brainstorms/ for a matching brainstorm. If found, read it fully — it contains architecture decisions, integration impact, and resolved questions that drive this plan. Also read any related existing plans in docs/plans/.
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.
- 9d ago First seen · 278 lines · 41 tokens per session scan A c2ba6d433028
pwf-plan is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 2,769 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-30.
Other commands, from other repositories
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
interview
Interview & refine a spec, task, or spec file in-depth.
tracker-sync
Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync).
audit
Audit .flow/memory/ entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry.
pilot
Single-tick autonomous build-loop conductor (one item, one stage per invocation; pipeline.chainStages==on chains make-pr after a fresh qa verdict); --backlog/--auto widens it to triage the whole open backlog.
features
Seed or maintain the committed user-POV feature map at .flow/features/.