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-setup)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-setup"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-setup/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-setup"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-setup.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.00045 | $0.01115 |
| Opus 5.5 | $0.00018 | $0.00446 |
| Sonnet 5.5 | $0.00009 | $0.00223 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
pwf-setup 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 2mo 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Project Workflow Skeleton
Use this command to bootstrap (or repair) the baseline workflow structure in docs/.
This command is intentionally deterministic: it creates missing structure without guessing architecture decisions.
Goals
- Ensure
docs/exists and has a predictable workflow structure. - Create missing directories and keep them in git using
.gitkeepwhen empty. - Ensure project-level operational override file exists:
docs/workflow/operational-overrides.md
- Ensure mandatory project baseline files exist:
docs/infrastructure.mddocs/architecture.mddocs/integrations.mddocs/environments.mddocs/glossary.md
- Ensure runbooks structure exists:
docs/runbooks/docs/runbooks/README.md
- Avoid destructive edits:
- Never delete existing docs.
- Never overwrite non-empty existing files unless explicitly requested by the user.
Important path boundary
Do not redefine this policy inline. Follow the canonical boundary rule:
rules/docs-scope-boundary.mdc
When running /pwf-setup, always create/update the project docs structure defined by that rule.
Required skeleton
Create these directories if missing:
docs/docs/brainstorms/docs/plans/docs/work-plans/docs/solutions/docs/solutions/patterns/docs/workflow/docs/runbooks/docs/modules/docs/features/docs/lambdas/docs/decisions/
For each empty directory above, create .gitkeep.
Required files (create if missing):
docs/README.md(index with links to core sections)docs/workflow/operational-overrides.md(project policy override file)docs/infrastructure.md(project infrastructure source of truth)docs/architecture.md(project architecture source of truth)docs/integrations.md(external systems and contract source of truth)docs/environments.md(environment matrix and deployment context source of truth)docs/glossary.md(domain and technical terminology source of truth)docs/runbooks/README.md(runbooks catalog and usage guide)
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.
- 2mo ago First seen · 158 lines · 45 tokens per session scan A 39e7b194f0f8
pwf-setup is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 1,115 once invoked, about $0.0002 per session on Opus 5.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
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
Resolve and squash merge one named, currently authorized pull request.
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".
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.