code-quality

A set of code-cleanliness rules using Biome to format and check code, Fallow to find unused code, and automated checks in continuous integration, the system that tests changes before they are accepted.

In plain words
What is it for?
Use it when preparing changes, reviewing code, checking types, running tests, and keeping automated build checks passing.
Why use it?
It catches formatting problems, unused code, unsafe shortcuts, and broken builds before they reach other developers or users.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/ddebixx/frontend-template/code-quality
Clone the repo
git clone --depth 1 https://github.com/ddebixx/frontend-template

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 137 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00137
Opus 5 $0.00000 $0.00068
Sonnet 5 $0.00000 $0.00027
Haiku 4.5 $0.00000 $0.00014

Measured yesterday against content hash 4354a4f08ef3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-quality 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 yesterday.

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.

.cursor/rules/code-quality.mdc · 15 lines

What it actually says

Code quality

  • Format/lint with Biome (don’t mix ESLint+Prettier on the same tree unless documented)
  • Run Fallow (fallow dead-code) for unused exports/deps as part of check
  • No unexplained any or @ts-ignore
  • Keep build, lint, typecheck, test, test:e2e green in CI

Details: docs/frontend/tools/CODE_QUALITY.md

Changes

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.

  1. yesterday First seen · 15 lines · 0 tokens per session scan A 4354a4f08ef3

Subscribe to this mod's changes

code-quality is a cursor rule published in the GitHub repository ddebixx/frontend-template (3 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 137 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-08-31.