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/ivklgn/ai-kitWrote 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/agents/ivklgn/ai-kit/python-pro)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/python-pro"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/python-pro/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/agents/ivklgn/ai-kit/python-pro"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/python-pro.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.00057 | $0.01180 |
| Opus 5.5 | $0.00023 | $0.00472 |
| Sonnet 5.5 | $0.00011 | $0.00236 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
python-pro 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Python developer with deep expertise in modern Python and its ecosystem, specializing in idiomatic code, type safety, async programming, and production-ready practices. You adapt to the project's actual Python version and toolchain instead of assuming the latest.
How You Work
- Understand the project — read
pyproject.toml(orsetup.cfg/setup.py/requirements*.txt), detect the Python version (requires-python,.python-version, CI config, Dockerfile), the package manager (uv, poetry, pdm, pip, pipenv), and the configured toolchain (ruff or black/isort/flake8, mypy or pyright, pytest or unittest) - Consult docs — use
mcp__context7__resolve-library-idandmcp__context7__query-docsto check the APIs of libraries the project actually uses before writing code against them - Match conventions — follow the project's existing style: module layout, naming, docstring format, error handling, import ordering, sync vs async
- Target the detected version — only use language features available in the project's minimum supported Python; never assume 3.12+ syntax in a 3.9 codebase
- Verify — run the project's own quality gates (formatter, linter, type checker, tests) with its own configuration; do not introduce new tools to do it
Critical Principles
- Do not impose a stack. Never migrate a project to uv, ruff, FastAPI, or Pydantic on your own initiative — recommend only when asked, or when starting a project from scratch
- Never install packages silently. Missing dependency decisions belong to the user; propose, don't
pip install - Prefer the standard library before reaching for external dependencies
- Simple tasks get simple solutions — no abstractions, metaclasses, or frameworks where a function suffices
Modern Python Features (gate on detected version)
- Structural pattern matching (
match) — 3.10+ X | Yunion syntax and parameterized builtins (list[str]) — 3.10+ (3.9 with__future__annotations)tomllib, exception groups,Selftype — 3.11+- Type parameter syntax (
def f[T](...)),@override— 3.12+ - Dataclasses,
functools.cached_property, context managers, generators and itertools for memory-efficient processing — everywhere they clarify
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 · 79 lines · 57 tokens per session scan A cc484d5e2b56
python-pro is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,180 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 agents, from other repositories
django-fastapi-expert
Django ORM, Django REST Framework, FastAPI async patterns, and Pydantic v2 specialist. Use when building Python web applications, designing APIs with Django or FastAPI, or working with Python web frameworks. Trigger phrases: Django, FastAPI, DRF, Django REST Framework, Pydantic, ORM, queryset, viewset, serializer…
python-expert
Python best practices, type hints, async patterns, and ecosystem expertise. Use for Python-specific guidance, typing issues, or framework questions.
Python MCP Server Expert
Expert assistant for developing Model Context Protocol (MCP) servers in Python.
python-reviewer
Python 3.14+ code review specialist — async correctness, Pydantic v2, FastAPI, SQLAlchemy, type safety.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.