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-brainstorm)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-brainstorm"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-brainstorm/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-brainstorm"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-brainstorm.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.00052 | $0.01703 |
| Opus 5 | $0.00026 | $0.00851 |
| Sonnet 5 | $0.00010 | $0.00341 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
pwf-brainstorm 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 10d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 1 — Explore and Decide Feature Scope
Note: The current year is 2026.
Use this command to transform an idea into concrete decisions (scope, architecture, constraints, and open questions) that become the direct input for /pwf-plan.
Feature Description
<feature_description> #$ARGUMENTS </feature_description>
If empty, ask: "What would you like to explore? Describe the feature, problem, or improvement."
Phase 0: Quick Clarity Check
Read the feature description. If requirements are already complete and scope is clear, ask:
"Requirements look clear. Proceed to
/pwf-plandirectly, or brainstorm first to surface integration impacts and architecture decisions?"
If the description is one vague sentence, ask one focused clarifying question before continuing. Otherwise proceed immediately.
Phase 1: Context Loading
Before spawning agents, read these directly (no agent needed):
docs/solutions/patterns/critical-patterns.md— always if it exists- Recent
docs/brainstorms/— check if there's an existing brainstorm for this topic - Recent
docs/plans/— check if there's already a plan that touches this area
Consolidate: what already exists, what's been decided before.
Phase 2: Research Agent Pack (Parallel)
Spawn the core research agents simultaneously using the Task tool (subagent_type: generalPurpose). Do not wait for one before starting the next. Pass the full feature description + context from Phase 1 to each.
Use collision-safe agent naming in prompts: psters-ai-workflow:<category>:<agent-name>.
Core agent 1 — Codebase Research (repo-research-analyst)
"Read and follow
agents/research/repo-research-analyst.md. Map all existing code related to:<feature_description>. Return: exact file paths, entity names, service method names, API routes, DTOs, components, Lambda repos, and which rules apply."
Core agent 2 — Integration & Impact Analysis (integration-impact-analyst)
"Read and follow
agents/research/integration-impact-analyst.md. Map every integration impact of:<feature_description>. For every entity, Lambda, notification type, settings section, and permission check: does this feature touch it, change it, or could break it? Focus on: entity changes and migration needs, Lambda pipeline impact, breaking changes with severity."
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.
- 10d ago First seen · 181 lines · 52 tokens per session scan A 95b7ea77f1d3
pwf-brainstorm is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 1,703 once invoked, about $0.0003 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".