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/synaptiai/prompt-decorators/060-coding-patternsgit clone --depth 1 https://github.com/synaptiai/prompt-decoratorsWhat 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.00000 | $0.00369 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
060-coding-patterns 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 2d 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
Coding Pattern Preferences
1.0.0
Context
- When writing new code or modifying existing code
- When implementing features or fixing bugs
- When refactoring or optimizing code
Requirements
- Prefer simple solutions over complex ones
- Avoid code duplication by checking for similar functionality elsewhere in the codebase
- Ensure code complies with pre-commit requirements
- Only make changes that are explicitly requested or well understood
- Exhaust all options within existing implementation before introducing new patterns
- Remove old implementations when introducing new ones to avoid duplicate logic
- Keep codebase clean and organized
- Avoid writing scripts in files, especially for one-time operations
- Refactor files exceeding 200-300 lines of code
- Use mocking data only for tests, never for dev or prod environments
- Never add stubbing or fake data patterns affecting dev or prod environments
- Never overwrite env files without explicit confirmation
Examples
base_total = sum(item.price for item in items)
return apply_discount(base_total) # Reusing existing functionality
# Reimplementing discount logic that already exists in utils.pricing
if base_total > 100:
return base_total * 0.9
else:
return base_total
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.
- 2d ago First seen · 53 lines · 369 tokens per session scan A fbfa97a45f53
060-coding-patterns is a cursor rule published in the GitHub repository synaptiai/prompt-decorators (43 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 369 tokens. 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
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
clarify-first-prompting
Clarify-first strategy: detect ambiguity, ask targeted questions, expand simple prompts into detailed specifications.
design-patterns
Design patterns (GoF) and file size conventions for sweagent TypeScript codebase.
serialization-rules
Unity serialization best practices.
websocket-implementation
This guide provides instructions for replacing the current polling mechanism with WebSocket communication.