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-doc)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-doc"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-doc.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.00161 | $0.02802 |
| Opus 5 | $0.00081 | $0.01401 |
| Sonnet 5 | $0.00032 | $0.00560 |
| Haiku 4.5 | $0.00016 | $0.00280 |
Grade A, and why
pwf-doc 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Force Technical Documentation by Scope
Note: The current year is 2026.
Use this command when you want explicit technical documentation output for a specific scope (module, feature, architecture, ADR, or global update). This is the general command to generate or update any documentation by described scope.
Work commands already update docs. /pwf-work, /pwf-work-plan, /pwf-work-light, and /pwf-work-tdd update docs as part of their workflow. Use /pwf-doc for explicit, scope-targeted documentation beyond that flow.
Anti-drift guidance: Before creating new docs, check if a related doc already exists. Prefer updating or syncing the existing doc instead of creating duplicates. This avoids drift and keeps documentation authoritative.
The living documentation lives in:
docs/lambdas/— Lambda and processor reposdocs/modules/— NestJS backend modules (or equivalent)docs/features/— Angular frontend features (or equivalent)docs/decisions/— Architecture Decision Records (ADRs)docs/architecture.md— System-wide architecture overview
Input
<doc_target> #$ARGUMENTS </pwf-doc_target>
If empty, show:
Usage:
/pwf-doc lambda <repo-name> Document a Lambda repo (e.g. /pwf-doc lambda email-classifier-lambda)
/pwf-doc lambdas Document ALL Lambda repos in parallel
/pwf-doc module <module-name> Document a backend module (e.g. /pwf-doc module projects)
/pwf-doc feature <feature-name> Document a frontend feature (e.g. /pwf-doc feature dashboard)
/pwf-doc architecture Generate/update docs/architecture.md
/pwf-doc update Scan all docs for staleness and contradictions
/pwf-doc adr "<decision>" Create an Architecture Decision Record
/pwf-doc custom "<target-and-pattern>" Generate/update any doc from user-described scope
/pwf-doc infrastructure Generate/update docs/infrastructure.md
Agent invocation
When spawning docs agents via Task tool, use collision-safe naming:
psters-ai-workflow:docs:<agent-name>.
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 · 268 lines · 161 tokens per session scan A a6a1092e803e
pwf-doc is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 161 tokens to every session and 2,802 once invoked, about $0.0008 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".