Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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-workspace)<a href="https://agentmods.dev/commands/j-pster/psters_ai_workflow/pwf-setup-workspace"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-setup-workspace/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-workspace"><img src="https://agentmods.dev/badge/commands/j-pster/psters_ai_workflow/pwf-setup-workspace.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.00041 | $0.00791 |
| Opus 5 | $0.00020 | $0.00396 |
| Sonnet 5 | $0.00008 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
pwf-setup-workspace 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Multi-Root Project Workspace
Use this command to create the recommended structure:
<ProjectName>_Repos/for code repositories (usually frontend and backend),<ProjectName>_Workspace/for docs,.cursor,.claude, and workspace-level assets,<ProjectName>.code-workspacefor a multi-root editor workspace.
This keeps code and workflow/docs concerns separated while still visible in one editor window.
Input
<workspace_setup_input> #$ARGUMENTS </workspace_setup_input>
If input is missing required fields, ask:
- Project name (example:
BDTX) - Base path where folders should be created (example:
/home/jpster/Repos) - Frontend repo folder name (default:
frontend) - Backend repo folder name (default:
backend) - Optional: existing repo paths to link instead of creating new empty folders
Rules
- Non-destructive by default:
- do not delete folders,
- do not move existing repos automatically without explicit user confirmation.
- If target folder exists, reuse it and report as "already existed".
- Always generate/update a workspace file in
<ProjectName>_Workspace/. - Keep paths explicit in the final report.
Target structure
Create or ensure:
<base>/<ProjectName>_Repos/<base>/<ProjectName>_Repos/<frontend-repo>/<base>/<ProjectName>_Repos/<backend-repo>/<base>/<ProjectName>_Workspace/<base>/<ProjectName>_Workspace/docs/<base>/<ProjectName>_Workspace/.cursor/<base>/<ProjectName>_Workspace/.claude/(if the user uses Claude Code)<base>/<ProjectName>_Workspace/<ProjectName>.code-workspace
Workspace file requirements
Write a valid JSON .code-workspace file with:
- one entry for workspace root (
.), - one entry for frontend repo path,
- one entry for backend repo path.
Use relative paths from <ProjectName>_Workspace/.
Example folders section:
{
"folders": [
{ "name": "Workspace", "path": "." },
{ "name": "Frontend", "path": "../<ProjectName>_Repos/<frontend-repo>" },
{ "name": "Backend", "path": "../<ProjectName>_Repos/<backend-repo>" }
]
}
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 · 101 lines · 41 tokens per session scan A 19242f5fa6df
pwf-setup-workspace is a command published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 791 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".