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.
git clone --depth 1 https://github.com/ConlinJoe/ai-platformWrote 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/conlinjoe/ai-platform/21-stack-architecture)<a href="https://agentmods.dev/rules/conlinjoe/ai-platform/21-stack-architecture"><img src="https://agentmods.dev/badge/rules/conlinjoe/ai-platform/21-stack-architecture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/conlinjoe/ai-platform/21-stack-architecture"><img src="https://agentmods.dev/badge/rules/conlinjoe/ai-platform/21-stack-architecture.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00957 |
| Opus 5.5 | $0.00000 | $0.00383 |
| Sonnet 5.5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
21-stack-architecture 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stack-native architecture
Apply this rule only after detecting the installed stack from repository evidence and reading applicable project contracts and ADRs. A familiar stack is not the default. If detection is uncertain, say so and do not apply an unrelated profile.
Canonical check, exceptions, and baseline behavior:
docs/contracts/features/stack-native-architecture.md. Decision:
ADR 0011.
Appearance, design references, and visual fidelity do not waive this rule. Implement the approved design with the stack's normal boundaries.
Template and MVC-style views
Use this profile for Blade and comparable server templates when the
file's nearest Composer package is Laravel, Roots/Sage/Acorn, or
another MVC-style template architecture. A nested package.json does
not hide that Composer package. A nearer Composer package that does not
declare Laravel or Roots is uncertain: do not inherit an ancestor Roots
or Laravel profile. A sibling package does not apply. Use that
framework's own layer names.
- Views render prepared data.
- Conditions, loops, formatting, components, and class selection may live in the template.
- Queries, persistence, business decisions, substantial data transformation, content parsing, and service orchestration belong in the controller, composer, presenter, service, or equivalent.
- Do not treat a template expression or helper call as prohibited logic by itself.
- Do not impose Laravel controllers, actions, or service class names on a framework that has a different structure.
Roots/Sage/Acorn: prepare fields and queries in composers or the
equivalent Acorn layer. get_field and WP_Query in a new Blade view
are not the presentation layer.
Components
Use this profile for React, Vue, Svelte, Solid, Preact, Angular, and similar component architectures.
- Follow that framework's component, hook, rendering, and data-access conventions.
- Do not apply MVC "no logic in views" restrictions to components.
- Do not invent a shared separation that conflicts with the installed framework.
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 · 106 lines · 957 tokens per session scan A 1c7cf6e3c758
21-stack-architecture is a cursor rule published in the GitHub repository ConlinJoe/ai-platform (2 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 957 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-10-30.
Other cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
css
Troy stylesheet conventions, layout debugging, and minification.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
z-index
Z-index layering conventions for consistent stacking.