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/prassanna-ravishankar/clearml-mcpWrote 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/prassanna-ravishankar/clearml-mcp/linting-philosophy)<a href="https://agentmods.dev/rules/prassanna-ravishankar/clearml-mcp/linting-philosophy"><img src="https://agentmods.dev/badge/rules/prassanna-ravishankar/clearml-mcp/linting-philosophy/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/prassanna-ravishankar/clearml-mcp/linting-philosophy"><img src="https://agentmods.dev/badge/rules/prassanna-ravishankar/clearml-mcp/linting-philosophy.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.00625 | $0.00625 |
| Opus 5 | $0.00313 | $0.00313 |
| Sonnet 5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
linting-philosophy 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linting Philosophy: File-Level Ignores Over Global
Core Principle
Use file-level ignores unless we truly need global ones. Different file types have different requirements - main source code should have strict linting, while tests and examples need appropriate flexibility.
Configuration Structure
Linting rules are configured in pyproject.toml [tool.ruff.lint] section:
Global Ignores (11 rules)
Only truly global style choices that apply project-wide:
- Exception handling style:
TRY003,EM101,EM102,B904,TRY300,BLE001 - Docstring formatting consistency:
D203,D205,D212,D400,D407,D415 - Import/typing consistency:
UP035,RUF013,COM812 - Build/maintenance:
CPY,ERA,W293
File-Level Ignores (per-file-ignores)
Test Files (tests/**/*.py)
11 ignores for test-specific patterns:
S101- Assert usage (required in tests)ANN*- Type annotations (relaxed for test helpers)PLR2004- Magic values (acceptable in test data)SIM103,B007,ARG*- Test helper patterns
Example Files (examples/**/*.py)
17 ignores for demo code flexibility:
T201- Print statements (examples need output)E402,E501- Import placement, line length (demo flexibility)F401- Unused imports (examples may import for demonstration)ANN*,D*- Relaxed typing and documentationBLE001- Broad exception handling (simplified examples)
Main Source (src/clearml_mcp/clearml_mcp.py)
4 specific ignores for legitimate architectural needs:
C901- Complex function (compare_tasks function)PERF401,C401- Performance patterns (specific instances)PLR0913- Argument count (specific functions)
Benefits
✅ Strict main code: Source files enforce high quality standards ✅ Appropriate flexibility: Tests and examples have relaxed rules where needed ✅ Clear rationale: Each ignore is documented with specific reasoning ✅ Maintainable: File-specific concerns handled at file level, not globally
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.
- 11d ago First seen · 61 lines · 625 tokens per session scan A 94857e50b240
linting-philosophy is a cursor rule published in the GitHub repository prassanna-ravishankar/clearml-mcp (16 stars, last pushed 2mo ago), licensed MIT. It adds 625 tokens to every session, about $0.0031 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
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.