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/operational-guardrails)<a href="https://agentmods.dev/rules/j-pster/psters_ai_workflow/operational-guardrails"><img src="https://agentmods.dev/badge/rules/j-pster/psters_ai_workflow/operational-guardrails/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/operational-guardrails"><img src="https://agentmods.dev/badge/rules/j-pster/psters_ai_workflow/operational-guardrails.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.00342 | $0.00342 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
operational-guardrails 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.
What it actually says
Operational Guardrails
Use this file as the default source of truth for repeated operational rules.
Policy hierarchy (who decides what)
- User explicit instruction in the current chat
- Project override file (if present):
docs/workflow/operational-overrides.md - This file (
rules/operational-guardrails.mdc) as default policy
If a project override exists, follow it for project-specific behavior. If no override exists, use the defaults below.
Default AWS operations policy (recommended, not forced)
- Run
aws sso login --profile <aws-profile>before AWS CLI commands when applicable. - Do not deploy through IAC/CDK unless project-specific rules explicitly allow it.
Default Lambda deployment policy
- Lambda deployment uses project deployment scripts only.
- Use command
/pwf-aws-lambda-deployfor guided Lambda deploy flow.
Completion claims (always required)
- No "done/fixed/passing" claims without fresh verification evidence.
- Include command, exit status, and key output in the completion message.
Verification evidence format
Command:executed commandResult:exit code/statusEvidence:key output linesLimitation:partial coverage or constraints (if any)
TypeORM migration discipline (default)
TypeORM migrations follow this atomic chain:
- Generate migration (
typeorm:generate) - Drift-check new migration (
schema-drift-detector) - Run migration locally immediately (
typeorm:run)
If step 3 fails, stop and fix before continuing other tasks.
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 · 50 lines · 342 tokens per session scan A d2c96e20ad8d
operational-guardrails is a cursor rule published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 342 tokens to every session, about $0.0017 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 cursor rules, from other repositories
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.
use-bun-instead-of-node-vite-npm-pnpm
../../CLAUDE.md.
shadcn-ui
This project includes the following components in @/components/ui (shadcn/ui + custom extensions), all compatible with Vite + React.
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.