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 skills add ludo-technologies/python-best-practices --skill toolinggit clone --depth 1 https://github.com/ludo-technologies/python-best-practicesWrote 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/skills/ludo-technologies/python-best-practices/tooling)<a href="https://agentmods.dev/skills/ludo-technologies/python-best-practices/tooling"><img src="https://agentmods.dev/badge/skills/ludo-technologies/python-best-practices/tooling/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/skills/ludo-technologies/python-best-practices/tooling"><img src="https://agentmods.dev/badge/skills/ludo-technologies/python-best-practices/tooling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.00921 |
| Opus 5.5 | $0.00024 | $0.00368 |
| Sonnet 5.5 | $0.00012 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
tooling 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 1mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Tooling
A comprehensive guide to Python development tools. Configuration best practices for analysis, linters, type checkers, formatters, test frameworks, and package managers.
Why These Tools Matter
To write high-quality Python code, we recommend adopting these tools:
- pyscn - Detect dead code, duplicates, and circular dependencies to prevent technical debt
- ruff - Catch bugs and style violations early with fast static analysis
- mypy - Find errors before runtime with type checking, also improves IDE completion
- pytest - Build confidence in changes with reliable tests
- uv - Improve developer experience with fast dependency management
Integrating these into CI/CD reduces code review burden and maintains consistent quality.
Categories
Analysis [HIGH]
Structural code analysis for quality assessment.
| Rule | Description |
|---|---|
| analysis-pyscn | Dead code, clones, dependencies, complexity with pyscn |
Linting [CRITICAL]
Static code analysis with ruff for consistent, high-quality code.
| Rule | Description |
|---|---|
| lint-ruff | Fast, comprehensive linting with ruff |
Type Checking [HIGH]
Static type checking with mypy for type safety and better IDE support.
| Rule | Description |
|---|---|
| type-mypy | Static type checking with mypy |
Formatting [HIGH]
Consistent code formatting with ruff format and import sorting.
| Rule | Description |
|---|---|
| fmt-ruff | Code formatting and import sorting with ruff |
Testing [HIGH]
Test framework configuration with pytest for reliable testing.
| Rule | Description |
|---|---|
| test-pytest | Testing with pytest, fixtures, and coverage |
Package Management [MEDIUM]
Modern Python packaging with uv and pyproject.toml.
| Rule | Description |
|---|---|
| pkg-uv | Fast package management with uv |
| pkg-pyproject | Project configuration with pyproject.toml |
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 131 lines · 60 tokens per session scan A f753bddb0776
tooling is a skill published in the GitHub repository ludo-technologies/python-best-practices (34 stars, last pushed 7d ago), licensed MIT. It adds 60 tokens to every session and 921 once invoked, about $0.0002 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-30.
Other skills, from other repositories
hypothesis-testing
Property-based testing with Hypothesis for discovering edge cases and validating invariants. Use when implementing comprehensive test coverage, testing complex logic with many inputs, or validating mathematical properties and invariants across input domains. Triggered by: hypothesis, property-based testing, @given…
test-harness
Generates pytest test suites with happy path, edge cases, error conditions, fixture scaffolding, mocks, async patterns. Triggers on: "generate tests", "write tests for", "test this function", "create test suite", "pytest for", "unit tests for", "mock strategy for".
python
Use when writing, reviewing, or modernizing Python 3.11+ code. Produces fully type-annotated modules, async I/O, dataclasses and protocols, pytest suites, and a lint/type gate built on ruff and mypy --strict. Trigger on "add type hints to this", "mypy is complaining", "convert this to asyncio", "set up pytest for this…
dev-python-quality
Use when Python-specific typing, async behavior, packaging, pytest, ruff/mypy, scripting, or performance quality is central to the request. Do not trigger for generic small code edits merely written in Python.
python-tdd
Use when implementing Python behavior test-first, reproducing bugs, characterizing legacy code, or applying red-green-refactor with pytest/unittest, fixtures, patch lookup, deterministic I/O and clocks, or Hypothesis properties. Covers coverage/mutation limits, not system-wide strategy or benchmarking.
python-testing
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.