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/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/code-style)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/code-style"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/code-style/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/louisbrulenaudet/monorepo-template/code-style"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/code-style.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.00543 |
| Opus 5.5 | $0.00000 | $0.00217 |
| Sonnet 5.5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
code-style 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 23d 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 — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Style
OXC decides style (lint-config.mdc): match the surrounding file, let oxfmt decide layout, and fix every warning - any warning fails CI.
- Handlers (routes, tools) stay thin: validate at the boundary, delegate I/O to a client or service module, then map the response. No business logic inline in a handler.
- Derive types from their source of truth instead of hand-writing shapes (contracts.mdc).
unknownbelongs only at an I/O boundary: a Zod parser, a type predicate's subject, an error /causehandler. Parse there and pass the domain type onward; never threadunknown/object/Record<string, unknown>through signatures or re-narrow with ad-hoctypeofchains.- Never annotate a literal wider than it is (
const handlers: Record<string, Handler> = { start }drops the known key): keep inference or usesatisfies. - Inline suppressions use the
oxlint-*form only, with a reason (// oxlint-disable-next-line <rule> -- <reason>);eslint-disable*comments are ignored and fail CI as unused directives. An unsafe assertion that must stay carries// oxlint-disable-next-line typescript/no-unsafe-type-assertion -- <invariant that makes it true>.
Strict compiler flags
strict.json in @repo/typescript-config rejects ordinary-looking code; write to these from the start:
| Flag | Forces |
|---|---|
exactOptionalPropertyTypes |
An optional prop may be absent, never explicitly undefined: { x: undefined } is not assignable to { x?: string } - omit the key |
noUncheckedIndexedAccess |
Array and index-signature reads yield T | undefined: narrow before use |
noPropertyAccessFromIndexSignature |
Index-signature keys use bracket notation, not dot |
verbatimModuleSyntax |
Type-only imports say import type, or they survive into JS |
erasableSyntaxOnly |
No runtime TS constructs - no enum, namespaces, or parameter properties (hence as const value sets) |
noImplicitOverride |
Subclass overrides are marked override |
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.
- 23d ago Changed · +8 lines f9752aec0028
- 25d ago Changed · +1 lines d84d1606891a
- 27d ago Changed · +3 lines 27a9f276dfc3
- 1mo ago First seen · 17 lines · 0 tokens per session scan A ad3150189557
code-style is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 543 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-09-03.
Other cursor rules, from other repositories
pr-review
Comprehensive pull request review from multiple perspectives.
code-analysis
Perform advanced code analysis with multiple inspection options.
general_clean_code_principles
Clean code principles for better readability.
review
Structured code review with severity ratings — CRITICAL/HIGH/MEDIUM/LOW.
analyze
Codebase analysis — complexity, coupling, dead code, tech debt hotspots.
optimize-dry-solid-principles-cursorrules-prompt-f
Cursor rules for optimization development with DRY and SOLID principles integration.