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/ci-cd-philosophy)<a href="https://agentmods.dev/rules/prassanna-ravishankar/clearml-mcp/ci-cd-philosophy"><img src="https://agentmods.dev/badge/rules/prassanna-ravishankar/clearml-mcp/ci-cd-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/ci-cd-philosophy"><img src="https://agentmods.dev/badge/rules/prassanna-ravishankar/clearml-mcp/ci-cd-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.00000 | $0.00703 |
| Opus 5 | $0.00000 | $0.00351 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
ci-cd-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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Philosophy: Comprehensive Quality Gates
Core Principle
Every change must pass all quality gates before merge. Use UV for fast, reliable builds and comprehensive testing across platforms and Python versions.
Pipeline Structure
Main CI workflow: .github/workflows/ci.yml
Quality Gates (All Required)
1. Lint Job (lint)
- Ruff check with GitHub format for PR annotations
- Ruff format check to ensure consistent formatting
- Ty type checking (non-blocking warnings, informational)
2. Test Job (test)
- Matrix testing: Ubuntu/macOS/Windows × Python 3.10-3.13
- pytest with verbose output and color
- Coverage reporting with 65% minimum threshold
- Parallel execution across all combinations
3. Pre-commit Job (pre-commit)
- All pre-commit hooks including basic checks, YAML/TOML/JSON validation
- Ruff integration for consistent linting and formatting
- End-of-file fixing and trailing whitespace removal
4. Build Job (build)
- UV build for wheel and source distribution
- Twine check for package validation
- Artifact upload for deployment readiness
5. Install-test Job (install-test)
- Cross-platform wheel installation testing
- CLI entry point verification across all platforms
- Import testing to ensure package integrity
Key Configuration Files
- Main CI: .github/workflows/ci.yml
- Coverage config: pyproject.toml
[tool.coverage.*] - Pre-commit: .pre-commit-config.yaml
- Package build: pyproject.toml
[build-system]
UV-First Approach
This project uses UV exclusively for:
- ✅ Dependency management and virtual environments
- ✅ Build and publish workflows
- ✅ Fast, reliable Python environment setup
- ❌ NOT Smithery (per project memory: uses uvx only for ClearML integration)
Quality Standards
- Test Coverage: 65% minimum (currently 69%)
- Platform Support: Ubuntu, macOS, Windows
- Python Support: 3.10, 3.11, 3.12, 3.13
- Code Quality: Ruff with file-level ignores for appropriate flexibility
- Type Safety: Ty checking with informational warnings
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 · 75 lines · 0 tokens per session scan A 65e12789c9d3
ci-cd-philosophy is a cursor rule published in the GitHub repository prassanna-ravishankar/clearml-mcp (16 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 703 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-30.
Other cursor rules, from other repositories
about-codebase
General information about the Lineai MCP Server codebase and its purpose.
validate-design-early
Ask for design approval before implementing 100+ lines.
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.