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/synmux/myriad/formatting-lintinggit clone --depth 1 https://github.com/synmux/myriadWrote 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/synmux/myriad/formatting-linting)<a href="https://agentmods.dev/rules/synmux/myriad/formatting-linting"><img src="https://agentmods.dev/badge/rules/synmux/myriad/formatting-linting.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.00580 | $0.00580 |
| Opus 5 | $0.00290 | $0.00290 |
| Sonnet 5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
formatting-linting 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 5d 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
Trunk
- Use trunk if
.trunk/trunk.yamlexists (https://trunk.io) - Check ignored issues with
trunk check --show-existing
Formatting
- Prefer
trunk fmt [filename]ortrunk fmt -a(all files)
Linting
- Prefer
trunk check [filename]ortrunk check -a(all files) - Auto-fix with
trunk check --fix [filename]ortrunk check --fix -a(all files) - Ignore warnings from
trunk-toolbox
TypeScript
- Regenerate types if necessary before linting.
bun run typesorbun run cf-typegen.
- When
biome.jsonexists:- Ensure
@biomejs/biomeis installed in devDependencies.- If not, add it and run
bun install.
- If not, add it and run
bun run biome check [filename]orbun run biome check(all files).- Safe fixes:
biome check --write [filename]orbiome check --write(all files). - Unsafe fixes:
biome check --write --unsafe [filename]orbiome check --write --unsafe(all files). - Validate unsafe fixes for functional parity.
- Ensure
- If a
lintscript (ie runnable withbun run lint) exists:- If it also runs
trunk, prefer it totrunk check. - If it doesn't, run it was well as
trunk check. - Also run Biome as described above if
biome.jsonexists.- Skip it if the
lintscript invokes it.
- Skip it if the
- If it also runs
- Run the
typecheckscript.- Example:
bun run typecheck. - Run
bun run tsc --noEmitdirectly if thetypecheckscript doesn't exist.
- Example:
Next.js Projects
- Also run
next lintvia package manager:- Bun:
bun run next lint - pnpm:
pnpm run next lint
- Bun:
Biome
- When enabled in trunk or
biome.jsonexists, run directly:biome check [filename]orbiome check(all files)- Safe fixes:
biome check --write [filename]orbiome check --write(all files) - Unsafe fixes:
biome check --write --unsafe [filename]orbiome check --write --unsafe(all files) - Validate unsafe fixes for functional parity
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.
- 5d ago First seen · 54 lines · 580 tokens per session scan A f1b2653a7fb7
formatting-linting is a cursor rule published in the GitHub repository synmux/myriad (2 stars, last pushed today), licensed MIT. It adds 580 tokens to every session, about $0.0029 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.