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-work-light)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-work-light"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-work-light/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-work-light"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-work-light.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.00030 | $0.00414 |
| Opus 5 | $0.00015 | $0.00207 |
| Sonnet 5 | $0.00006 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
pwf-work-light 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.
What it actually says
Execute Lightweight Work
Use this for truly small/local changes.
Apply skills/using-psters-workflow/SKILL.md at start.
Trivial scope criteria
All must be true:
- <= 2 files expected to change
- no new entities/migrations/endpoints
- no auth/security model changes
- no cross-repo architectural impact
If any criterion fails, use /pwf-work or /pwf-work-plan instead.
Workflow
- Apply
skills/docs-baseline-loading/SKILL.mdand execute baseline loading before coding. - Read
docs/solutions/patterns/critical-patterns.md(if exists), directly relevant module/feature doc, anddocs/runbooks/README.mdwhen operational behavior is touched. - Implement targeted change.
- Run minimal verification command(s) relevant to the change.
- Run focused documentation check:
- update docs only if contract/behavior changed,
- otherwise report "no doc impact" with reason.
Work commands update docs as part of the workflow; use
/pwf-docor/pwf-doc-capturefor explicit scope-targeted documentation.
- Finish with verification evidence.
Verification Evidence Format
Use the shared evidence format from rules/operational-guardrails.mdc.
Project-specific override is allowed via docs/workflow/operational-overrides.md (if present).
Guardrails
- If scope expands during work, stop and switch to
/pwf-work. - Do not use for migrations, risky deploy changes, or broad refactors.
Next Recommended Commands
/pwf-reviewwhen change risk is not purely cosmetic/pwf-commit-changesafter verification
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 · 52 lines · 30 tokens per session scan A b1dd0d3c230b
pwf-work-light is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 414 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
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".