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/lint-config)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/lint-config"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/lint-config/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/lint-config"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/lint-config.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.00843 |
| Opus 5.5 | $0.00000 | $0.00337 |
| Sonnet 5.5 | $0.00000 | $0.00169 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
lint-config 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 7d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint and Static-Analysis Config
OXC is the source of truth: .oxlintrc.json (lint) and .oxfmtrc.json (format); React Doctor adds doctor.config.jsonc. This rule holds the rationale for their non-obvious settings; the authoring consequences live in code-style.mdc, tailwind.mdc, and react.mdc.
oxlint
denyWarnings: true: any warning fails CI.typeAware: true, but oxlint's experimentaloptions.typeCheckstays off: type checking stays with tsc (turbo run check-types), which keeps Turbo's per-package caching and--affected.respectEslintDisableDirectives: falsewithreportUnusedDisableDirectives: "error":eslint-disable*comments are ignored, and any stray one fails CI.- The
apps/front-*/src/**override restates the fullpluginslist on purpose: override plugins extend the base, but trimming the list toreact/jsx-a11yenablesreact/react-in-jsx-scope(dozens of false errors). Hook rules andjsx-a11ylive in that override; no ESLint toolchain exists alongside. - OXC always runs from the repo root because
better-tailwindcssresolvessettings.better-tailwindcss.entryPointagainst the process CWD, not against.oxlintrc.json:oxlint .insideapps/front-appresolvesapps/front-app/apps/front-app/src/index.css, so the theme-aware rules print a "No tailwind css entry point found" banner on every message andno-unknown-classesrejects every@themetoken. Scope by path instead (pnpm --filter=front-app run lint:check).
better-tailwindcss
- Runs as an oxlint JS plugin on
apps/front-*/src/**/*.{ts,tsx};entryPointpoints atapps/front-app/src/index.cssso the theme is known. - Enabled, all
error:enforce-canonical-classes,no-concatenated-classes,no-conflicting-classes,no-deprecated-classes(catches v3 names in v4),no-duplicate-classes,no-unknown-classes,no-unnecessary-whitespace. The four that need the theme:enforce-canonical-classes,no-conflicting-classes,no-deprecated-classes,no-unknown-classes.no-unknown-classesis the strongest guard for AI-authored markup. enforce-consistent-class-orderstays off:oxfmtowns ordering throughsortTailwindcss.stylesheet(theprettier-plugin-tailwindcssalgorithm, resolved relative to.oxfmtrc.json, so CWD-independent), and the two must not disagree.enforce-consistent-line-wrappingstays off:oxfmtowns JS/JSX layout, and the two would fight overclassNamewrapping.
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.
- 7d ago First seen · 30 lines · 0 tokens per session scan A 3b5b67a32949
lint-config is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (18 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 843 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-30.
Other cursor rules, from other repositories
mcp-inspector-debugging
Debugging and verifying MCP servers using the MCP Inspector UI with Playwright automation.
five
Use the "Five Whys" root cause analysis technique to deeply understand problems.
check
Perform comprehensive code quality and security checks.
clean
Fix all code formatting and quality issues in the entire codebase.
bug-fix
Streamline bug fixing workflow from issue creation to pull request.
diagnose
Systematic root cause diagnosis — confidence scoring, investigation budgeting, hypothesis branching.