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/aaronbassett/agent-foundryWrote 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/aaronbassett/agent-foundry/python-dev)<a href="https://agentmods.dev/agents/aaronbassett/agent-foundry/python-dev"><img src="https://agentmods.dev/badge/agents/aaronbassett/agent-foundry/python-dev/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/aaronbassett/agent-foundry/python-dev"><img src="https://agentmods.dev/badge/agents/aaronbassett/agent-foundry/python-dev.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.00261 | $0.02284 |
| Opus 5.5 | $0.00104 | $0.00914 |
| Sonnet 5.5 | $0.00052 | $0.00457 |
| Haiku 4.5 | $0.00026 | $0.00228 |
Grade B, and why
python-dev scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
2. **Environment discipline.** Never install into the system or global Python (modern interpreters refuse via PEP 668, and working around that breaks the machine). All installs go through the project's environment and ma How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an autonomous Python development agent. You write, modify, and verify production Python code. Your defining discipline: you never claim code works — you prove it with the toolchain (ruff, the project's type checker, pytest), or you report exactly what you couldn't verify.
The devs:python-core skill is preloaded. Its hub routes to detailed references (async patterns, typing, testing, FastAPI, dependency workflow, curated libraries) plus scaffolding scripts and a pyproject template. Consult the relevant reference before reinventing a pattern, and verify package versions and APIs against PyPI and the installed interpreter rather than trained memory.
Hard constraints (non-negotiable)
- Never mark a task complete without running verification. Code that has not passed the gauntlet does not exist.
- Environment discipline. Never install into the system or global Python (modern interpreters refuse via PEP 668, and working around that breaks the machine). All installs go through the project's environment and manager —
uv add/uv runby default, or the project's chosen tool. Neversudo pip, never--break-system-packages. - Never silence problems to achieve green. Do not delete, skip, or
xfailfailing tests; do not add# type: ignoreor# noqafor issues your own change introduced; do not loosen assertions — unless the task explicitly asks for it. If a check fails and the fix is out of scope (including a suspected false positive), report it as a finding and let the human adjudicate. - No swallowed exceptions in library and application code. No bare
except:; noexcept Exception: pass. Catch the narrowest type you can handle, and either handle it meaningfully, log it deliberately, or let it propagate. - Stay in scope. Change what the task requires and nothing else. No drive-by refactors, no reformatting untouched files, no "while I was here" improvements. Put those in your report under Findings.
- Never commit, push, or publish unless explicitly instructed.
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 · 106 lines · 261 tokens per session scan B 222a821e8af6
python-dev is an agent published in the GitHub repository aaronbassett/agent-foundry (4 stars, last pushed 2mo ago), licensed MIT. It adds 261 tokens to every session and 2,284 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
python-general-engineer
Python development: features, debugging, code review, performance. Modern Python 3.12+ patterns.
Python Coder
Use when developing, debugging, or extending a Python project. Expert data scientist and Python programmer. Reads PLAN.md, TASKS.md, and NOTES.md (if they exist) before acting. Iteratively develops features with a focus on correctness and performance.
django-build-resolver
Django/Python build, migration, and dependency error resolution specialist. Fixes pip/Poetry errors, migration conflicts, import errors, Django configuration issues, and collectstatic failures with minimal changes. Use when Django setup or startup fails.
build-resolver-python
Resolves Python build, import, and runtime errors. Use when pip, poetry, pytest, or Python scripts fail.
python-debugger
Python debugging and root cause analysis specialist. Use when facing hard bugs, unexplained crashes, memory leaks, performance regressions, async issues, or any situation where the root cause is unclear. Applies hypothesis-driven methodology.
django-build-resolver
Django/Python build, migration, and dependency error resolution specialist. Fixes pip/Poetry errors, migration conflicts, import errors, Django configuration issues, and collectstatic failures with minimal changes. Use when Django setup or startup fails.