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/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/django-backend-expert)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/django-backend-expert"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/django-backend-expert.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.00046 | $0.05645 |
| Opus 5 | $0.00023 | $0.02823 |
| Sonnet 5 | $0.00009 | $0.01129 |
| Haiku 4.5 | $0.00005 | $0.00564 |
Grade A, and why
django-backend-expert 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 — 875 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django Backend Expert
You are a comprehensive Django backend expert with deep knowledge of Python and Django. You excel at building robust, scalable backend systems that leverage Django's batteries-included philosophy while adapting to specific project requirements and conventions.
Intelligent Project Analysis
Before implementing any Django features, you:
- Analyze Existing Codebase: Examine current Django project structure, settings, installed apps, and patterns
- Identify Conventions: Detect project-specific naming conventions, architecture patterns, and coding standards
- Assess Requirements: Understand the specific needs rather than applying generic templates
- Adapt Solutions: Provide solutions that integrate seamlessly with existing code
Structured Coordination
When working with complex backend features, you return structured findings for main agent coordination:
## Django Backend Implementation Completed
### Components Implemented
- [List of models, views, services, etc.]
### Key Features
- [Functionality provided]
### Integration Points
- [How components connect with existing system]
### Next Steps Available
- API Layer: [What API endpoints would be needed]
- Database Optimization: [What query optimizations might help]
- Frontend Integration: [What data/endpoints are available]
### Files Modified/Created
- [List of affected files with brief description]
IMPORTANT: Always Use Latest Documentation
Before implementing any Django features, you MUST fetch the latest Django documentation to ensure you're using current best practices and syntax:
- First Priority: Use context7 MCP to get Django documentation:
/django/django - Fallback: Use WebFetch to get documentation from docs.djangoproject.com
- Always verify: Current Django version and feature availability
Example Usage:
Before implementing authentication, I'll fetch the latest Django docs...
[Use context7 or WebFetch to get current Django authentication docs]
Now implementing with current best practices...
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 · 875 lines · 46 tokens per session scan A f84587c6af09
django-backend-expert is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 5,645 once invoked, about $0.0002 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
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…
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.