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/sunra-ai/sunra-clients/lintergit clone --depth 1 https://github.com/sunra-ai/sunra-clientsWrote 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/sunra-ai/sunra-clients/linter)<a href="https://agentmods.dev/rules/sunra-ai/sunra-clients/linter"><img src="https://agentmods.dev/badge/rules/sunra-ai/sunra-clients/linter.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.01081 |
| Opus 5 | $0.00000 | $0.00541 |
| Sonnet 5 | $0.00000 | $0.00216 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
linter 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Formatting and Linting Rules
General Principles
- Consistency: Maintain consistent code style across all files in the project
- Readability: Prioritize code readability and maintainability
- Best Practices: Follow language-specific best practices and conventions
- Automation: Use automated tools to enforce formatting and catch common issues
Line Length and Formatting
- Maximum line length: 120 characters for all languages
- No multiple consecutive blank lines: Maximum of 1 blank line between code blocks
- Trailing whitespace: Remove all trailing whitespace
- Indentation: Use consistent indentation (2 spaces for JS/TS, 4 spaces for Python, 2 spaces for Java/Kotlin)
Python Specific Rules
Tools
- Use
rufffor both linting and formatting - Configuration is in
pyproject.tomlunder[tool.ruff]
Linting Rules
- A: flake8-builtins - Avoid shadowing Python built-ins
- B: flake8-bugbear - Catch common bugs and design problems
- C4: flake8-comprehensions - Improve list/dict/set comprehensions
- E: pycodestyle errors - Style guide enforcement
- F: Pyflakes - Catch undefined names and imports
- I: isort - Sort imports consistently
- UP: pyupgrade - Upgrade syntax for newer Python versions
Type Hints
- Use modern union syntax
T | Noneinstead ofOptional[T]when possible - Always include type hints for function parameters and return values
- Use
from __future__ import annotationsfor forward references
Naming Conventions
- Functions and variables:
snake_case - Classes:
PascalCase - Constants:
UPPER_SNAKE_CASE - Avoid single-letter variable names except for short loops
Commands
- Format:
ruff format .ormake format - Lint:
ruff check .ormake lint - Auto-fix:
ruff check --fix .
JavaScript/TypeScript Rules
Tools
- Use ESLint for linting
- Use Prettier for formatting (if configured)
- Follow the project's ESLint configuration
General Rules
- Use
constby default,letwhen reassignment is needed - Prefer arrow functions for callbacks
- Use template literals for string interpolation
- Don't use semicolons when possible
- Prefer
===over==
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 · 151 lines · 0 tokens per session scan A 7da370c6ac99
linter is a cursor rule published in the GitHub repository sunra-ai/sunra-clients (7 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,081 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-04.
Other cursor rules, from other repositories
production-review-panel
Four-persona senior engineering panel for production-grade code analysis and refactoring.
omni-rewriter
Omni-Rewriter prompt-expansion framework conventions.
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
code-review
BMAD BMM Agent: code-review.
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.