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/khaledsaeed18/node-express-boilerplate/architecturegit clone --depth 1 https://github.com/KhaledSaeed18/node-express-boilerplateWhat 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.00354 | $0.00354 |
| Opus 5 | $0.00177 | $0.00177 |
| Sonnet 5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
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 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
Layered Architecture
Routes → Controllers → Services → Repositories → Prisma (PostgreSQL).
Every new resource requires exactly these five files, in this order:
| File | Purpose |
|---|---|
src/validations/<name>.validation.ts |
Zod v4 schemas + RequestHandler exports |
src/repository/<name>.repository.ts |
I<Name>Repository interface + class extending BaseRepository |
src/services/<name>.service.ts |
I<Name>Service interface + class |
src/controllers/<name>.controller.ts |
I<Name>Controller interface + class extending BaseController |
src/routes/<name>.route.ts |
class extending BaseRoute, exports router instance |
After creating those files:
- Register repository, service, and controller in
src/container/index.tsfollowing the existing init pattern. - Mount the route in
src/app.tsat/api/v1/<name>. - Export all interfaces and classes from the barrel files (
src/repository/index.ts,src/services/index.ts,src/controllers/index.ts).
DI Container
Container (singleton in src/container/index.ts) is the only place where new Repository/Service/Controller() is called. Access instances in routes via this.container.get<Name>Controller().
Entry Points
src/index.ts— binds the port only (importappin tests without binding)src/app.ts— all middleware and route mounting
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 · 34 lines · 354 tokens per session scan A 99825b14af9f
architecture is a cursor rule published in the GitHub repository KhaledSaeed18/node-express-boilerplate (33 stars, last pushed 9d ago), licensed MIT. It adds 354 tokens to every session, about $0.0018 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
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, loader validates into section diagnostics).
directory-layout
Directory layout rules for SQL family vs concrete targets.
no-contract-data-patching-in-tests
Never patch raw contract data in tests; use real emitted fixtures or a user-facing authoring surface.