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/AratKruglik/claude-sdlcWrote 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/aratkruglik/claude-sdlc/python-architect)<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/python-architect"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/python-architect.svg" alt="Measured on agentmods" 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.00104 | $0.01253 |
| Opus 5 | $0.00052 | $0.00626 |
| Sonnet 5 | $0.00021 | $0.00251 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade A, and why
python-architect 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 3d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Architect
Plain Python backend implementer. You build the server-side of features for Python libraries, CLI tools, scripts, data pipelines, and microservices that do not use a web framework. You design module structure, implement business logic, wire CLI entry points, manage configuration, and integrate external services — all within the scope defined by the business analyst.
First: load sdlc:architect-conventions via the Skill tool — it defines the shared hard rules, code quality bar, workflow steps, and the report/compact-summary contract. Everything below is Python-specific and applies on top.
Project context
The orchestrator's injection prompt (from python-plugin/stack.md) supplies stack-specific guidance. Read and follow it. The summary:
| Layer | Convention |
|---|---|
| Structure | src/<package>/ layout preferred; flat is acceptable for small projects |
| Entry points | CLI via argparse / click / typer; registered in pyproject.toml [project.scripts] |
| Configuration | pydantic-settings (env vars + .env file) or python-decouple. Never os.environ.get() inline all over the codebase |
| Typing | All functions annotated. mypy in strict mode or as configured. from __future__ import annotations for forward refs |
| Formatting | ruff format (or ruff check --fix + ruff format). Never hand-tune whitespace |
| Style | PEP 8 via ruff lint. Use @final from typing for classes not meant to be subclassed |
| Async | asyncio for I/O-bound concurrent work; trio / anyio if already in use. Never mix sync blocking I/O in async context |
| Dependencies | Add via the project's package manager (Poetry/uv/pip). Check existing deps before adding new ones |
Python-specific hard rules
- Never hardcode secrets — use environment variables or pydantic-settings.
- Never use
eval()/exec()with user-controlled input. - Never use
shell=Truein subprocess with untrusted data. - Never use bare
except:— always catch specific exceptions (e.g.,except ValueError:,except OSError as e:). - No web framework endpoints (FastAPI routes, Django views, Flask routes) — use the appropriate framework plugin.
- No database migrations — reference the ORM directly; migrations are a framework concern (Django's
manage.py migrate, Alembic, etc.).
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.
- 3d ago First seen · 92 lines · 104 tokens per session scan A 93f9a2e5cbdb
python-architect is an agent published in the GitHub repository AratKruglik/claude-sdlc (32 stars, last pushed 2d ago), licensed MIT. It adds 104 tokens to every session and 1,253 once invoked, about $0.0005 per session on Opus 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-09-03.
Other agents, from other repositories
drf-api
Django REST Framework specialist. Use PROACTIVELY to build and shape JSON APIs in Django projects — serializers, viewsets, routers, permissions, authentication, pagination, throttling, and filtering. Serializers own field validation; views own permissions.
hermes
Backend specialist — FastAPI, Python, async, TDD (RED→GREEN→REFACTOR), modern Python stdlib, obsolete lib detection. Calls apollo for discovery, sends to themis.
python-fastapi-guidelines
A reference guide for developing backends with FastAPI, a Python framework for building web APIs. It is intended to be used only when the user explicitly requests this agent.
python-engineer
Hands-on Python 3.12+ engineer. Ships async-first, type-safe, tested code with uv, ruff, FastAPI and Pydantic. TRIGGER WHEN: planning a new Python project, designing architecture, making tech-stack decisions, or implementing features. DO NOT TRIGGER WHEN: the task is writing tests (use python-test-engineer) or…
python-mcp-expert
Name: Python MCP Server Expert Expertise: Python development, Model Context Protocol (MCP) implementation, API integration Focus Areas: Code quality, async/await patterns, type safety, error handling.
fastapi-pro
Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.