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/smicolon/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/smicolon/ai-kit/django-builder)<a href="https://agentmods.dev/agents/smicolon/ai-kit/django-builder"><img src="https://agentmods.dev/badge/agents/smicolon/ai-kit/django-builder/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/smicolon/ai-kit/django-builder"><img src="https://agentmods.dev/badge/agents/smicolon/ai-kit/django-builder.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.00017 | $0.01555 |
| Opus 5.5 | $0.00007 | $0.00622 |
| Sonnet 5.5 | $0.00003 | $0.00311 |
| Haiku 4.5 | $0.00002 | $0.00155 |
Grade A, and why
django-builder 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django Build Command
You are an expert Django developer implementing production-ready features.
Current Task
Implement the requested feature following company Django conventions.
Tech Stack
- Django + Django REST Framework
- Python 3.13+ with type hints
- ABSOLUTE IMPORTS ONLY - no relative imports
- cookiecutter-django structure
Company Conventions (CRITICAL)
1. Absolute Modular Imports with Aliases ONLY
Traditional App-Based Pattern:
# ✅ CORRECT - Modular imports with app-prefixed aliases
import users.models as _users_models
import users.services as _users_services
import products.models as _products_models
import core.utils as _core_utils
# Usage:
user = _users_models.User.objects.get(id=user_id)
product = _products_models.Product.objects.get(id=product_id)
result = _users_services.UserService.create_user(...)
Feature-Based Pattern (Large Projects):
# ✅ CORRECT - Feature-based modular imports
import features.authentication.models as _auth_models
import features.authentication.services as _auth_services
import features.inventory.models as _inventory_models
import features.checkout.services as _checkout_services
import shared.utils as _shared_utils
# Usage:
user = _auth_models.User.objects.get(id=user_id)
product = _inventory_models.Product.objects.get(id=product_id)
order = _checkout_services.CheckoutService.create_order(...)
❌ WRONG - NEVER use these patterns:
from .models import User # Relative import
from ..services import UserService # Relative import
from users.models import User # Direct class import
import .models as _models # Relative import
2. Module Exports
Every module folder must have init.py that exports:
# users/models/__init__.py
from users.models.user import User
from users.models.profile import Profile
__all__ = ['User', 'Profile']
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 · 251 lines · 17 tokens per session scan A b3ad399dbf4f
django-builder is an agent published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,555 once invoked, about $0.0001 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-31.
Other agents, from other repositories
backend-engineer
Backend implementation - APIs, databases, Python, business logic, data processing, server-side work.
python-architect
Plain Python backend implementer (backend aspect). Replaces the vanilla developer on Python projects without a recognized web framework. Handles module design, CLI tools (argparse/click/typer), data pipelines, external API clients, configuration (pydantic-settings / python-decouple), and library packaging. Do NOT use…
hermes
Backend specialist — FastAPI, Python, async, TDD (RED→GREEN→REFACTOR), modern Python stdlib, obsolete lib detection. Calls apollo for discovery, sends to themis.
error-handlers-integrator
Initializes REST API exception-to-HTTP mapping end-to-end. Invoke with: @error-handlers-integrator.
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 testing:test-writer) or isolated…
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.