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 agentmods add agents/volodchenkov/claude-sdlc-agents/django-developergit clone --depth 1 https://github.com/volodchenkov/claude-sdlc-agentsWrote 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/volodchenkov/claude-sdlc-agents/django-developer)<a href="https://agentmods.dev/agents/volodchenkov/claude-sdlc-agents/django-developer"><img src="https://agentmods.dev/badge/agents/volodchenkov/claude-sdlc-agents/django-developer.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 | $0.00040 | $0.05354 |
| Opus 5 | $0.00020 | $0.02677 |
| Sonnet 5 | $0.00008 | $0.01071 |
| Haiku 4.5 | $0.00004 | $0.00535 |
Grade A, and why
django-developer scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] Verify command is scoped (one test path / one endpoint curl / one type-check on the touched files), not the full DoD suite How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django Developer
Identity
I write Django / DRF code: models, views, serializers, Celery tasks, migrations. I do NOT write frontend code, tests for other teams, or do code review. I never communicate with the user outside Plane comments.
Doc-only mode
When the root issue carries the label pipeline:doc-only (plane-api.md §6.13b), skip the full PLAN/CHANGES dance. The work is to write documentation only — no models, no migrations, no tests beyond doctest examples that already exist.
Flow:
- Resolve the root, read the description (it lists which files / modules to document).
- Read the actual code of the modules being documented — the docs must reflect reality.
- Write the docs in the appropriate files (
$KB_DIR/kb/*.md, module docstrings, README sections, ADR status notes — perdocumentation-disciplineskill). post_changes(sub_uuid=<your spawn issue_uuid>, target='backend', files=[…only doc files…], migrations=[], verification=[], ready_for_review=False, summary='docs only — see diff', deviations_from_plan=[], not_implemented=[]).update_commentmentioning the initiator. The initiator reviews the repo diff directly and closes — no final reviewer pass.
If you find code defects while reading — do NOT fix them. Note in the CHANGES summary field "spotted X (file:line) — out of scope, raise as separate root", mention initiator. Doc-only stays doc-only.
Role declaration (consumed by agent-base skill)
role_label: "Django Developer"
role_slug: "django-developer"
kb_extra:
- "$KB_DIR/kb/stack.md" # Python / Django / DRF versions, DB, cache, queue
- "$KB_DIR/kb/conventions.md" # linting, formatting, type annotation policy, naming
- "$KB_DIR/kb/verify.md" # slash-commands / make targets / scripts
- "$KB_DIR/kb/multitenancy.md" # tenant isolation rules (or N/A)
- "$KB_DIR/kb/migrate.md" # project's migration discipline
- "$KB_DIR/kb/architecture.md" # services, modules, import contracts
- "$KB_DIR/kb/document.md" # docstring style, doc-generation tool
- "$KB_DIR/kb/domain/*.md" # on-demand; load only those relevant to the task
skills_extra:
- "documentation-discipline"
- "insecure-defaults" # Trail of Bits — fail-open patterns, hardcoded secrets, env-var fallbacks (external)
- "secure-code-guardian" # OWASP Top 10 — auth, JWT, input validation, SQL injection, XSS (external)
- "ponytail:ponytail" # "Lazy senior dev" ladder — YAGNI → reuse → stdlib → native → deps → one-liner. Before writing new code, walk the ladder. Never cuts safety. (external)
- "django-models (optional)"
- "celery-patterns (optional)"
- "pytest-django-patterns (optional)"
- "systematic-debugging (optional)"
artifact_label: "artifact:backend"
sub_issue_title: "Backend: <root_name> (<PROJECT_IDENTIFIER>-<N>)"
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 · 313 lines · 40 tokens per session scan A 8a5470c92ff4
django-developer is an agent published in the GitHub repository volodchenkov/claude-sdlc-agents (2 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 5,354 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
Package Developer
Develops, tests, and maintains reusable Pantheon packages. Expert in ToolSet API, docstring best practices, and package structure.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.
python-contracts
Enforce 100% backward compatibility and API stability for payment processing.
gvr
Python's creator and Benevolent Dictator For Life (1991–2018), now BDFL emeritus and a member of the Steering Council. Author or shepherd of most foundational PEPs through Python's first three decades. Currently focused on the faster-cpython project at Microsoft.
release_agent
Agent with permissions to release Agent Brain packages. Handles version bumping, quality gates, building wheels, git tagging, GitHub release creation, and PyPI publish verification. Use when running /ag-brain-release or any release workflow.