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/markdown-style)<a href="https://agentmods.dev/rules/louisbrulenaudet/monorepo-template/markdown-style"><img src="https://agentmods.dev/badge/rules/louisbrulenaudet/monorepo-template/markdown-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.00312 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
markdown-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 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.
What it actually says
Markdown Style
Markdown in this repo is not hard-wrapped. One line per paragraph, one line per list item, one line per table row. Existing files run 250-700 characters on a single line and that is correct, not a defect to fix. There is no markdown formatter - oxfmt does not touch .md - so nothing will reflow this for you and nothing will reflow it back.
- Never split a sentence across lines, and never reflow a paragraph to a column limit. A paragraph is one line, however long. A bullet is one line, however long.
- Frontmatter string values stay on one line too. Do not fold a long
description:across continuation lines. - Structural lines keep their own line: headings, table rows, and the contents of fenced code blocks.
- A GitHub alert marker stays on its own line above its body:
> [!NOTE]then> <body>. Collapsing the marker onto the body line stops GitHub rendering it as an alert. - Applies to every
.mdand.mdcin the repo, includingREADME.md,AGENTS.md,CLAUDE.md,.changeset/**, and both rule trees.
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 · 16 lines · 312 tokens per session scan A 79ea85a44f09
markdown-style is a cursor rule published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 312 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
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.
swift-argument-parser
Documentation and usage patterns for Swift Argument Parser for command-line tools.
competition-details
Exclude competition details from agent work.
release-version-bump-auto
Apply when the user is creating or preparing a release, version bump, tag, publish, or deploy. Validates semantic version bumps against change analysis (breaking/feat/fix), blocks inappropriate bumps, and guides major/minor/patch or custom version choice. Use for release workflows, package versioning, and…
react_hooks
React Hooks best practices for frontend package.