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/louisbrulenaudet/monorepo-template/code-stylegit 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.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.1 | $0.00000 | $0.00366 |
| Opus 5 | $0.00000 | $0.00183 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
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 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
Code Style
OXC is the source of truth: .oxlintrc.json (lint) and .oxfmtrc.json (format). Do not restyle to match personal habits - match the surrounding file and let oxfmt decide layout. These rules run with denyWarnings: true / maxWarnings: 0, so any warning fails CI. Do not silence a rule, add a blanket ignore, or cast through any / as unknown to clear an error - fix the cause (see guardrails.mdc).
Discipline
- Keep route/tool handlers thin: validate at the boundary, delegate I/O to a client or service module, then map the response. Business logic does not belong inline in the handler.
- Prefer native type inference (see type-inference.mdc) over hand-written shapes.
- Lint and format run as a whole-repo OXC pass from the root - never
cdinto a package and runoxlint .(breaks context-aware Tailwind rules). See Scoping in rootAGENTS.md. - Inline suppressions use the
oxlint-*form only (// oxlint-disable-next-line <rule>with a reason)..oxlintrc.jsonsetsrespectEslintDisableDirectives: false, soeslint-disable*comments are ignored by the linter and, viareportUnusedDisableDirectives: "error", any stray one fails CI.
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 · 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 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 366 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
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.
competition-details
Exclude competition details from agent work.
swift-argument-parser
Documentation and usage patterns for Swift Argument Parser for command-line tools.
testing
Always use vitest for testing. Use describe/it blocks.
update-docs
You will generate LLM-optimized documentation with concrete file references and flexible formatting.