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/saropa/saropa_lintsWrote 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/saropa/saropa_lints/saropa_lints_instructions)<a href="https://agentmods.dev/rules/saropa/saropa_lints/saropa_lints_instructions"><img src="https://agentmods.dev/badge/rules/saropa/saropa_lints/saropa_lints_instructions/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/saropa/saropa_lints/saropa_lints_instructions"><img src="https://agentmods.dev/badge/rules/saropa/saropa_lints/saropa_lints_instructions.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.00512 | $0.00512 |
| Opus 5.5 | $0.00205 | $0.00205 |
| Sonnet 5.5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
saropa_lints_instructions 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 2mo 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
Guidelines when working on the saropa_lints codebase (Dart custom lint rules package).
Essential Files to Update
- New rule: Register in lib/src/rules/all_rules.dart and lib/src/tiers.dart. Add entry to ROADMAP.md.
- Structural changes: Update CODEBASE_INDEX.md when adding utilities or moving files.
- Before publish: Update CHANGELOG.md.
Workflow
- Adding a rule: Implement in appropriate
lib/src/rules/*_rules.dart, extendDartLintRuleorSaropaLintRule, add DartDoc with Bad/Good examples, register in all_rules.dart and tiers.dart, add ROADMAP entry, add fixture inexample/(mark violations with// LINT) and unit test intest/. - Validation: Run
/analyze,/test,/format. UseSkill(lint-rules)when adding or modifying rules. - Example dirs: All
example*/must be inanalysis_options.yamlunderanalyzer > exclude(they contain intentional violations).
You Must NOT
- Add or support
// ignore:or// ignore_for_file:(no quick fixes that insert ignore; no custom ignore-detection in rules). Fix the rule or the code instead. - Add quick fixes that only insert a
// TODO: ...comment; fixes must make a real code change that resolves the violation. - Add Co-authored-by, AI attribution, or emojis to commit messages.
Principles
- Search first: Check CODEBASE_INDEX.md and lib/src utilities before adding new code.
- ProjectContext: Use for package detection, platform detection, file classification—do not reimplement.
- Type checking over string matching; early returns for simple checks.
- Code quality: Functions ≤50 lines, parameters ≤3, nesting ≤3, files ≤200 lines (self-reviewer enforces).
Commands and Skills
/analyze,/test,/format,/review,/commitas in CLAUDE.md.Skill(lint-rules)for rule work;Skill(publishing)for releasing.
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.
- 2mo ago Changed · -9 tokens per session 512f76bbb8b0
- 2mo ago First seen · 38 lines · 521 tokens per session scan A 639e9e261f27
saropa_lints_instructions is a cursor rule published in the GitHub repository saropa/saropa_lints (10 stars, last pushed 4d ago), licensed MIT. It adds 512 tokens to every session, about $0.0020 per session on Opus 5.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.
saropa_lints_instructions compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| saropa_lints_instructionssaropa/saropa_lints | Cursor rule | 10 | 4d ago | MIT | A | 512 | Cursor |
| fixysfAskri/archguardian | Cursor rule | 4 | 8mo ago | MIT | A | 0 | Cursor |
| validation-harnessBlackLeg15/desafio_bloc_1 | Cursor rule | 7 | 3mo ago | none | A | 0 | Cursor |
| testingBlackLeg15/desafio_bloc_1 | Cursor rule | 7 | 3mo ago | none | A | 0 | Cursor |
| create-analyzegurkanfikretgunak/masterfabric_core | Cursor rule | 16 | 8mo ago | none | A | 0 | Cursor |
| error-handlingnedcodes-ok/cursor-doctor | Cursor rule | 10 | 8mo ago | MIT | A | 493 | Cursor |
| ponytailDietrichGebert/ponytail | Cursor rule | 185k | 8d ago | MIT | A | 604 | Cursor |