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/linuxfoundation/lfx-self-serve/pre-commit-lint-formatgit clone --depth 1 https://github.com/linuxfoundation/lfx-self-serveWhat 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 | $0.00376 | $0.00376 |
| Opus 5 | $0.00188 | $0.00188 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
pre-commit-lint-format 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.
What it actually says
Pre-commit: format, lint, and unit tests before every commit
Always run all three checks on the changed files before staging and committing. A missed step is the most common cause of a red CI check.
1. Format
# Format changed files
npx prettier --write "<path(s) to changed files>"
# Verify formatting passes CI check
yarn format:check "<path(s) to changed files>"
The CI "Code Quality Checks" job runs yarn format:check over all files and fails if any file has Prettier diffs.
2. Lint
# Lint (repo-wide; use --filter to scope when faster)
yarn lint
3. Unit tests
# Full test suite (server vitest + Angular builder)
yarn test
The CI "Code Quality Checks" job runs yarn test across all packages. Always run this locally before committing — the most common test failures are:
- A new method added to a service but not added to the service mock in the component spec (causes
TypeError: this.fooService.newMethod is not a functionas an unhandled exception at runtime, which CI counts as a test failure even if the assertion tests all pass) - A shared constant renamed without updating the spec that imports it
When adding a method to a service that already has a spec and a mock provider, always add the method to the mock's useValue object in the spec.
Run order
Format → lint → test. If any step fails, fix before committing.
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.
- yesterday First seen · 46 lines · 376 tokens per session scan A 370b3e9394eb
pre-commit-lint-format is a cursor rule published in the GitHub repository linuxfoundation/lfx-self-serve (11 stars, last pushed 2d ago), licensed MIT. It adds 376 tokens to every session, about $0.0019 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-30.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.