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/bitflight-devops/skilllintWrote 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/bitflight-devops/skilllint/typing-and-design-standards)<a href="https://agentmods.dev/rules/bitflight-devops/skilllint/typing-and-design-standards"><img src="https://agentmods.dev/badge/rules/bitflight-devops/skilllint/typing-and-design-standards/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/bitflight-devops/skilllint/typing-and-design-standards"><img src="https://agentmods.dev/badge/rules/bitflight-devops/skilllint/typing-and-design-standards.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.00474 | $0.00474 |
| Opus 5.5 | $0.00190 | $0.00190 |
| Sonnet 5.5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
typing-and-design-standards 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 18d 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
Typing and design standards (no compromise)
Typing
- Follow
docs/TYPING_POLICY.mdas the source of truth. The type gate isuv run ty check packages/(seepyproject.toml[tool.ty.*]). - No using
Any, uncheckedcast(), ortype: ignore/ty: ignoreto silence the checker without a documented, localized reason (e.g. test-only@no_type_checkwith a short rationale). cast()only after a real proof step (runtime check, Pydantic validation, or documented library guarantee).cast()is not validation.- Ingress: isolate unknown shape in boundary-style modules (
*_ingest.py,boundary/, etc.); validate with Pydantic; pass concrete types inward.
SOLID and structure
- Single responsibility: one module/function, one reason to change.
- Open/closed: extend via new types or adapters, not sprawling conditionals.
- Liskov: subtypes honor contracts; no surprise narrowing of behavior.
- Interface segregation: small
Protocols / facades; avoid fat “god” interfaces. - Dependency inversion: depend on abstractions at boundaries; wire concretions at the edge.
DRY and clarity
- DRY real duplication only—do not abstract for two copies or speculative reuse.
- Prefer explicit names and small helpers over clever one-offs.
- Match existing project patterns (imports, error handling, test layout per
AGENTS.md).
Non-negotiables
- No invented constraints (magic numbers, timeouts, length limits) without a spec, config, or comment citing the source (
AGENTS.md). - No drive-by refactors unrelated to the task; every changed line should serve the request.
- Prefer one principled fix over a quick hack; if a shortcut is unavoidable, isolate it, document why, and keep it out of domain code.
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.
- 18d ago Changed · -2 tokens per session acb55515415f
- 1mo ago First seen · 35 lines · 476 tokens per session scan A fb7c685614fb
typing-and-design-standards is a cursor rule published in the GitHub repository bitflight-devops/skilllint (7 stars, last pushed 5d ago), licensed MIT. It adds 474 tokens to every session, about $0.0019 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.
Other cursor rules, from other repositories
python-3-brutal-audit
Phase-based brutal audit workflow for Python projects - on-demand architectural review.
python-standards
Python coding standards for source files.
python
Python development guidelines — PEP 8, type hints, error handling, async patterns, packaging, and testing. Applied when working with Python code.
python-backend
Python Backend Execution Agent (FastAPI / Django / Flask).
python-3-brutal-audit
Phase-based brutal audit workflow for Python projects - on-demand architectural review.
sweep-style
Audit xrspatial modules for PEP8 violations, unused imports, import ordering drift, and bug-prone style anti-patterns.