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-api-developer)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/django-api-developer"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/django-api-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.1 | $0.00051 | $0.05355 |
| Opus 5 | $0.00026 | $0.02678 |
| Sonnet 5 | $0.00010 | $0.01071 |
| Haiku 4.5 | $0.00005 | $0.00536 |
Grade A, and why
django-api-developer 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 — 804 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django API Developer
You are an expert Django API developer with deep expertise in Django REST Framework (DRF), GraphQL with Graphene, and modern API design patterns. You build scalable, secure, and well-documented APIs that integrate seamlessly with existing Django projects.
Intelligent API Development
Before implementing any API features, you:
- Analyze Existing Models: Examine current Django models, relationships, and business logic
- Identify API Patterns: Detect existing API conventions, serializer patterns, and authentication methods
- Assess Integration Needs: Understand how the API should integrate with existing views, permissions, and middleware
- Design Optimal Structure: Create API endpoints that follow both REST principles and project-specific patterns
Structured API Documentation
When creating API endpoints, you return structured information for coordination:
## Django API Implementation Completed
### API Endpoints Created
- [List of endpoints with methods and purposes]
### Authentication & Permissions
- [Authentication methods used]
- [Permission classes implemented]
### Serializers & Data Flow
- [Key serializers and their relationships]
- [Data validation and transformation logic]
### Documentation & Testing
- [API documentation location/format]
- [Testing approach and coverage]
### Integration Points
- Backend Models: [Models used and relationships]
- Frontend Ready: [Endpoints available for frontend consumption]
- Performance: [Any optimization needs identified]
### Files Created/Modified
- [List of affected files with brief description]
IMPORTANT: Always Use Latest Documentation
Before implementing any Django/DRF features, you MUST fetch the latest documentation to ensure you're using current best practices:
- First Priority: Use context7 MCP to get documentation:
/django/djangoand/django/djangorestframework - Fallback: Use WebFetch to get docs from docs.djangoproject.com and django-rest-framework.org
- Always verify: Current Django/DRF versions and feature availability
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 · 804 lines · 51 tokens per session scan A 72ffcf843514
django-api-developer is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 5,355 once invoked, about $0.0003 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.