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/tecnomanu/agent-rules-kit/06-architecture-managementgit clone --depth 1 https://github.com/tecnomanu/agent-rules-kitWrote 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/tecnomanu/agent-rules-kit/06-architecture-management)<a href="https://agentmods.dev/rules/tecnomanu/agent-rules-kit/06-architecture-management"><img src="https://agentmods.dev/badge/rules/tecnomanu/agent-rules-kit/06-architecture-management.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.00735 | $0.00735 |
| Opus 5 | $0.00367 | $0.00367 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
06-architecture-management 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Management
This document explains how different architecture styles are managed for each stack in Agent Rules Kit.
Package Management
Always use pnpm to install new packages or to run commands.
Architecture Structure
Each stack can have multiple architecture styles organized in the following way:
templates/
└── stacks/
├── laravel/
│ ├── base/ # Common rules for all Laravel projects
│ ├── architectures/ # Architecture-specific rules
│ │ ├── standard/ # Standard MVC architecture
│ │ ├── ddd/ # Domain-Driven Design architecture
│ │ └── hexagonal/ # Hexagonal (Ports & Adapters) architecture
│ └── v10-11/ # Version-specific overlays
│
└── nextjs/
├── base/ # Common rules for all Next.js projects
├── architectures/ # Architecture-specific rules
│ ├── app/ # App Router architecture (Next.js 13+)
│ └── pages/ # Pages Router architecture
└── v13/ # Version-specific overlays
Configuration
Architectures are configured in templates/kit-config.json:
{
"[stack_name]": {
"default_architecture": "standard",
"version_ranges": {
"8": {
"name": "Laravel 8-9",
"range_name": "v8-9"
},
"9": {
"name": "Laravel 8-9",
"range_name": "v8-9"
},
"10": {
"name": "Laravel 10-11",
"range_name": "v10-11"
}
},
"globs": [
"<root>/app/**/*.php",
"<root>/routes/**/*.php"
],
"architectures": {
"standard": {
"name": "Standard Architecture",
"globs": [...],
"pattern_rules": {...}
},
"ddd": {
"name": "Domain-Driven Design",
"globs": [...],
"pattern_rules": {...}
}
}
}
}
Key configuration properties:
default_architecture: The default architecture to use if none is specifiedversion_ranges: Maps major versions to version range informationname: Human-readable name for the version rangerange_name: Identifier used for version-specific directories
globs: File patterns to apply rules toarchitectures: Available architecture styles for the stack- Each architecture can have its own
globsandpattern_rules
- Each architecture can have its own
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 · 111 lines · 735 tokens per session scan A 03481aa3bd23
06-architecture-management is a cursor rule published in the GitHub repository tecnomanu/agent-rules-kit (35 stars, last pushed 11mo ago), licensed ISC. It adds 735 tokens to every session, about $0.0037 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
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.