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/rules/j-pster/psters_ai_workflow/docs-scope-boundary)<a href="https://agentmods.dev/rules/j-pster/psters_ai_workflow/docs-scope-boundary"><img src="https://agentmods.dev/badge/rules/j-pster/psters_ai_workflow/docs-scope-boundary/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/rules/j-pster/psters_ai_workflow/docs-scope-boundary"><img src="https://agentmods.dev/badge/rules/j-pster/psters_ai_workflow/docs-scope-boundary.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.00322 | $0.00322 |
| Opus 5.5 | $0.00129 | $0.00129 |
| Sonnet 5.5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
docs-scope-boundary 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 1mo 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
Docs Scope Boundary
Never mix these two docs/ scopes:
- Plugin docs scope (this repository):
- Root
docs/in this workspace documents the plugin itself.
- Root
- Project docs scope (target project):
docs/created/updated by workflow commands in the user's project.
Required behavior
- For
/pwf-setup,/pwf-work,/pwf-work-plan,/pwf-work-light,/pwf-work-tdd, always operate on the target project docs tree. - Do not treat this repository root
docs/as the target project docs unless the user explicitly says this repo is the target project. - If scope is ambiguous, ask which docs scope to use before writing files.
Canonical project docs paths
Use these paths (no pwf- directory prefixes):
docs/infrastructure.mddocs/architecture.mddocs/integrations.mddocs/environments.mddocs/glossary.mddocs/runbooks/docs/runbooks/README.mddocs/brainstorms/docs/plans/docs/work-plans/docs/workflow/operational-overrides.mddocs/solutions/docs/modules/docs/features/docs/lambdas/docs/decisions/
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.
- 1mo ago First seen · 41 lines · 322 tokens per session scan A 47b622050ba3
docs-scope-boundary is a cursor rule published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 7mo ago), licensed MIT. It adds 322 tokens to every session, about $0.0013 per session on Opus 5.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 cursor rules, from other repositories
context-discipline
Manage AI context window efficiently - read before write, no re-reads, tool-call budgets, one-pass discipline.
token-efficiency
Token efficiency rules - eliminate waste in AI output, enforce read-before-write, prevent iteration cycles.
conservative-file-creation
Check for existing files before creating. Be conservative about new files and code.
repository-layout
Canonical map of repo folders and docs.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.