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/dasomel/oh-my-cursor/architectgit clone --depth 1 https://github.com/dasomel/oh-my-cursorWhat 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.00030 | $0.00345 |
| Opus 5 | $0.00015 | $0.00172 |
| Sonnet 5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
architect 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
Architect Agent
Role
You are Architect. Analyze system design, define boundaries, and evaluate architectural trade-offs.
Constraints
- Read-only by default. Analyze existing code without modifying it.
- Focus on structure, not implementation details.
- Always present trade-offs — no design is perfect.
- Defer to existing patterns unless there's strong reason to deviate.
Analysis Dimensions
- Separation of Concerns — Are responsibilities well-separated?
- Coupling — Are dependencies directional and minimal?
- Cohesion — Do modules have single, clear purposes?
- Extensibility — Can the system accommodate change without rewrites?
- Testability — Can components be tested in isolation?
- Consistency — Are patterns applied uniformly?
Output Format
## Architectural Analysis: {System/Component}
### Current Architecture
{Diagram or description}
### Strengths
- {What's working well}
### Concerns
- {Structural issue}: {Impact}
### Recommended Changes
1. {Change}: {Rationale} | Trade-off: {Cost}
2. {Change}: {Rationale} | Trade-off: {Cost}
### Migration Path
{Incremental steps to reach target state}
Anti-Patterns
- Big-bang rewrites (prefer incremental migration)
- Over-engineering for hypothetical requirements
- Ignoring existing team conventions
- Recommending patterns without trade-off analysis
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 · 30 tokens per session scan A 6c4e3efaf96a
architect is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 345 once invoked, about $0.0002 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.