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-runbook)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-doc-runbook"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-doc-runbook/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-doc-runbook"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-doc-runbook.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.00038 | $0.00479 |
| Opus 5 | $0.00019 | $0.00239 |
| Sonnet 5 | $0.00008 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
pwf-doc-runbook 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 11d 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
Build Operational Runbooks
Use this command to create or update operational runbooks for services and critical workflows. Runbooks should be practical during incidents: short, specific, and executable.
Input
<doc_runbook_target> #$ARGUMENTS </doc_runbook_target>
If empty, ask:
"Which runbook should I create or update? (example: payments-api or deploy-backend)"
Special target:
index-> refreshdocs/runbooks/README.md
Canonical paths
- Runbook file:
docs/runbooks/<slug>.md - Index file:
docs/runbooks/README.md
Workflow
- Ensure
docs/runbooks/exists. - Determine whether this is
createorupdate:- if runbook file exists, update it in place (anti-drift),
- if not, create new canonical file.
- Read related source docs before writing:
docs/infrastructure.mddocs/architecture.mddocs/integrations.mddocs/environments.md
- Write/update runbook with concrete command paths, dependencies, and failure handling.
- Update
docs/runbooks/README.mdwith runbook index entry.
Required runbook structure
OverviewScope and OwnershipAccess and PrerequisitesMonitoring and AlertsCommon Failure ScenariosDiagnosis StepsMitigation and RecoveryRollback ProcedureEscalationPost-Incident Checklist
Output
Report:
- runbook path created/updated,
- index updates,
- missing operational data still needed from the user.
Next Recommended Commands
/pwf-doc-foundation allwhen baseline docs are stale or incomplete/pwf-doc updatefor full consistency scan/pwf-reviewif runbook changes reflect high-risk operational changes
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.
- 11d ago First seen · 70 lines · 38 tokens per session scan A 303171f03c13
pwf-doc-runbook is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 479 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".