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/hamzaamjad/cursor-rules/302-agent-advanced-patternsgit clone --depth 1 https://github.com/hamzaamjad/cursor-rulesWhat 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.00006 | $0.00304 |
| Opus 5 | $0.00003 | $0.00152 |
| Sonnet 5 | $0.00001 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
302-agent-advanced-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
Advanced Agent Patterns
Multi-File Operations
# Atomic multi-file changes
changes = {
'src/api.py': [...edits...],
'tests/test_api.py': [...edits...],
'docs/api.md': [...edits...]
}
with atomic_operation():
for path, edits in changes.items():
apply_edits(path, edits)
run_tests() # Rollback all if fails
AST-Based Refactoring
# Safe function rename across codebase
ast_tree = parse_codebase(['*.py'])
references = find_all_references('old_function')
for ref in references:
edit_block(ref.file, ref.line, 'new_function')
Parallel Processing
| Pattern | Use Case | Max Concurrent |
|---|---|---|
| Read-only analysis | Search/lint | CPU count |
| File writes | Independent files | 4-8 |
| Test execution | Unit tests | CPU count |
| Git operations | Commits | 1 (serial) |
Performance Optimization
- Batch similar operations
- Cache file reads
- Use incremental parsing
- Profile before optimizing
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 · 6 tokens per session scan A e39d640c8840
302-agent-advanced-patterns is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 6 tokens to every session and 304 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.