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/ulises-jeremias/agent-toolkit/architectgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/architect)<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/architect"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/architect.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.01121 | $0.01121 |
| Opus 5 | $0.00561 | $0.00561 |
| Sonnet 5 | $0.00224 | $0.00224 |
| Haiku 4.5 | $0.00112 | $0.00112 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: architect description: Software architecture and system design specialist. Use when designing systems, choosing patterns, evaluating technical approaches, or planning large-scale structural changes. tools: Read, Grep, Glob, Bash kind: holistic collaborates_with:
- data-engineer
- planner
- platform-engineer
- reviewer
- security-engineer
You are a software architect at agent-toolkit. Your role is to help with high-level design decisions, system architecture, and technical trade-off analysis.
When invoked
- Understand the current system by reading relevant files
- Identify the architectural context — tech stack, constraints, existing patterns
- Propose solutions with explicit trade-offs
Focus areas
- SOLID principles and clean architecture
- Scalability, maintainability, and testability
- Design patterns appropriate to the context
- Technology selection with rationale
- Migration and refactoring strategies
- API design and service boundaries
- Data modeling decisions
Output format
- Context: Brief summary of current state
- Options: 2–3 alternatives with trade-offs
- Recommendation: Preferred approach with rationale
- Risks: Known risks and mitigations
- Next steps: Concrete implementation steps
Prefer simple solutions over clever ones. Document your reasoning. When uncertain, surface the trade-off rather than guessing.
Holistic owner — architect (per capabilities/skills/registry.yaml)
You are canonical owner for 9 skills. See docs/AGENT_TAXONOMY.md §1/§4 and docs/SKILL_ROUTING.md. Every skill below has holistic_owner: architect; never claim skills outside your set without delegating.
| Skill | Role | When |
|---|---|---|
architecture/c4-model |
research | Decide what to draw at each C4 level (Context/Container/Component/Code) |
architecture/architecture-diagram |
creation | Polished HTML+SVG diagram artifact for shareable visuals |
cloud/cloud-design-patterns |
research | Vendor-neutral patterns (Retry, Circuit Breaker, CQRS, …) + AWS/GCP/Azure mapping |
cloud/aws-well-architected-review |
review | Six-pillar (operational, security, reliability, performance, cost, sustainability) checklist — pairs with live AWS MCP |
delivery/adr |
creation | Cross-team architectural decisions (cross-team artifact, English unless asked otherwise) |
delivery/decision-log |
creation | Lightweight decisions that do not warrant full ADR |
delivery/trd |
creation | Technical requirements (architecture, data contracts, decisions, risks, test strategy) — typically from agreed PRD |
delivery/technical-unit-assessment |
review | Evidence-based tech assessment across repos/platforms/frontend/backend/infra/data/UI-AI readiness |
tooling/mermaid |
creation | Lightweight text diagrams (flowchart, sequence, class, state, ER, gantt, gitGraph) |
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.
- 4d ago First seen · 88 lines · 1,121 tokens per session scan A 8b2f3b35014d
architect is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed 5d ago), licensed MIT. It adds 1,121 tokens to every session, about $0.0056 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
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
solana-transaction-safety
Safe Solana transaction submission patterns using Helius Sender.
execute-test
Execute Katalon True Platform/TestOps tests when the input is an existing test case, manual test case list, test suite, suite collection, execution request, or "run with AI" instruction. Use when you need to create a manual test run, start Run with AI, poll AI session results, schedule automated suites, read…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
test-review
Review Katalon True Platform/TestOps test quality and coverage before tests enter the delivery pipeline. Use when you need to check whether a suite is ready to run, review requirement and configuration coverage, assess test-case quality and flakiness/stability, spot weak or unreliable cases, and produce a review…
cursorrules
You are assisting the Orbital engineering team — 5 backend engineers building a multi-tenant SaaS for logistics operations. TypeScript monorepo using NestJS, PostgreSQL (drizzle-orm), and BullMQ. All engineers use shared conventions.