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-help)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-help"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-help.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.00029 | $0.00959 |
| Opus 5 | $0.00015 | $0.00479 |
| Sonnet 5 | $0.00006 | $0.00192 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
pwf-help 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 8d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Psters Workflow Command Guide
Use this command to explain the workflow to the user in a simple, practical way. This is a read-only guidance command: it should not edit files, run deployments, or create commits.
What to explain first
- The workflow intent:
- predictable execution,
- docs-first context,
- explicit user control over quality gates.
- The default flow:
/pwf-brainstorm->/pwf-plan->/pwf-work-plan
- Optional quality gates:
/pwf-clarify,/pwf-checklist,/pwf-analyze,/pwf-review
- Documentation and learnings commands:
/pwf-doc,/pwf-doc-foundation,/pwf-doc-runbook,/pwf-doc-capture,/pwf-doc-refresh
- Closing and delivery commands:
/pwf-commit-changes,/pwf-aws-lambda-deploy(when relevant)
- Workspace bootstrap command (when starting from scratch):
/pwf-setup-workspace
Explain all commands (quick map)
/pwf-help— explain all commands and workflow path/pwf-setup— initialize or repair docs workflow structure/pwf-setup-workspace— create recommended multi-root*_Repos+*_Workspacelayout/pwf-brainstorm— explore idea, scope, and architecture options/pwf-plan— convert context into executable phases/tasks/pwf-clarify— resolve ambiguity before execution (optional)/pwf-checklist— generate requirement quality gates (optional)/pwf-analyze— run read-only consistency analysis (optional)/pwf-work-plan— execute one planned phase/pwf-work— execute direct focused implementation outside a formal plan/pwf-work-light— fast path for trivial/local changes/pwf-work-tdd— tests-first execution when explicitly requested/pwf-review— heavy multi-agent review pass/pwf-doc— force canonical technical documentation updates/pwf-doc-foundation— create/refresh core project docs baseline/pwf-doc-runbook— create/refresh operational runbooks/pwf-doc-capture— register reusable learnings and patterns/pwf-doc-refresh— curate/refreshdocs/solutions/lifecycle/pwf-commit-changes— create structured, ticket-aware commits/pwf-aws-lambda-deploy— deploy Lambda changes with guarded script flow
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.
- 8d ago First seen · 85 lines · 29 tokens per session scan A 1e8e835c2d87
pwf-help is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 959 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-30.
Other commands, from other repositories
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
spec-research
A requirements-research command that turns a request into a set of constraints and checkable success criteria. It explores the relevant parts of a project in parallel and creates a structured proposal.
triage
Triage Linear issue with comprehensive analysis.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Manually trigger plan-sync to update downstream task specs after implementation drift.
slack-gif-creator
Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".