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.
npx agentmods add rules/j-pster/psters_ai_workflow/command-naming-prefixesgit 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/command-naming-prefixes)<a href="https://agentmods.dev/rules/j-pster/psters_ai_workflow/command-naming-prefixes"><img src="https://agentmods.dev/badge/rules/j-pster/psters_ai_workflow/command-naming-prefixes.svg" alt="Measured on agentmods" 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 | $0.00213 | $0.00213 |
| Opus 5 | $0.00106 | $0.00106 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
command-naming-prefixes 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 5d 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
Command Naming Prefixes
Use explicit technology prefixes for commands that are bound to a specific platform, provider, or framework.
Rule
- If a command is technology-specific, its name MUST start with that technology prefix.
- If a command is provider-specific, include the provider prefix first.
- Keep framework-agnostic commands generic (do not add unnecessary prefixes).
Naming format
- Preferred format:
<provider>-<technology>-<action> - Example for AWS Lambda deploy:
aws-lambda-deploy
Examples
aws-lambda-deploy(AWS-specific Lambda deploy workflow)stripe-webhook-sync(Stripe-specific operation)angular-component-audit(Angular-specific operation)
Anti-examples
deploy-lambda(missing provider/technology prefix)deploy(too generic for a tech-specific operation)
When creating or renaming commands, always apply this convention and update workflow docs accordingly.
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.
- 5d ago First seen · 33 lines · 213 tokens per session scan A 763b495bc0f0
command-naming-prefixes is a cursor rule published in the GitHub repository J-Pster/Psters_AI_Workflow (290 stars, last pushed 5mo ago), licensed MIT. It adds 213 tokens to every session, about $0.0011 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.
research-before-suggesting
Never make up features, APIs, or config options. Research before suggesting technical solutions.
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.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.