django-modern-rest is a typed REST framework for Django, the Python web framework, for building APIs that exchange data with clients over HTTP. It is for Django developers who need asynchronous support, schema validation, multiple data formats, and generated OpenAPI descriptions. The catalogue add-ons provide plugins and skills for developing with the framework.
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 skills add wemake-services/django-modern-rest --skill dmr-from-django-ninjagit clone --depth 1 https://github.com/wemake-services/django-modern-restWrote 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/skills/wemake-services/django-modern-rest/dmr-from-django-ninja)<a href="https://agentmods.dev/skills/wemake-services/django-modern-rest/dmr-from-django-ninja"><img src="https://agentmods.dev/badge/skills/wemake-services/django-modern-rest/dmr-from-django-ninja/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/skills/wemake-services/django-modern-rest/dmr-from-django-ninja"><img src="https://agentmods.dev/badge/skills/wemake-services/django-modern-rest/dmr-from-django-ninja.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.00068 | $0.01909 |
| Opus 5.5 | $0.00027 | $0.00764 |
| Sonnet 5.5 | $0.00014 | $0.00382 |
| Haiku 4.5 | $0.00007 | $0.00191 |
Grade A, and why
dmr-from-django-ninja 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 yesterday.
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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DMR from django-ninja
Overview
Migrate django-ninja / ninja-extra transport layer to django-modern-rest incrementally.
Keep business logic unchanged unless user explicitly asks.
Required docs (always reference first):
- DMR LLM docs: https://django-modern-rest.readthedocs.io/llms.txt
- Local map: references/ninja-to-dmr-map.md
Migration Policy
- Default mode: strict transport parity.
- Preserve by default: paths, methods, request/response schemas, status codes, headers, auth semantics, throttling semantics.
- If user approves drift (for example switching to DMR-native error format/status), stop forcing legacy behavior and document this as
approved drift. - Never mix implicit drift: every intentional mismatch must be explicitly listed.
- Do not preserve Ninja infrastructure internals as implementation strategy. Keep observable contracts, but realize them with DMR + project-native libraries.
Workflow
Inventory Ninja surface
- Read project API entrypoints and URL wiring first.
- Find usages of:
NinjaExtraAPI,api_controller,http_get/http_post/...,ninja.Schema,ninja_jwt, Ninja exception handlers, Ninja throttles. - Build per-endpoint migration matrix:
- path, method, auth, throttle, input DTO, output DTO,
- expected statuses, expected headers,
- known error paths.
Inventory project-native batteries (required)
- Before writing adapters, inspect existing project libraries and integrations that should power the migrated transport layer.
- Prefer libraries already used by the project ("Django batteries") through DMR mechanisms over custom wrappers.
- Examples:
- rate limiting: prefer
django-ratelimitintegration when it exists, instead of wrapping Ninja throttles, - auth/account lockout: prefer existing project auth stack (e.g. axes/middleware) instead of reusing Ninja-specific auth internals.
- rate limiting: prefer
Freeze observable behavior
- Capture behavior from existing tests + DTOs + routing.
- Mark blocking mismatches before coding:
- route/method changes,
- schema field changes,
- auth/throttle changes,
- status/header changes.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 196 lines · 68 tokens per session scan A 0dda436c77f1
dmr-from-django-ninja is a skill published in the GitHub repository wemake-services/django-modern-rest (1,519 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 1,909 once invoked, about $0.0003 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-10-26.
Other skills, from other repositories
api-testing-patterns
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.
add-console-command
Add or change a Symfony console command using this repository's command, dependency-injection, input/output, and testing conventions.
add-event-listener
Create or update Symfony event listeners or Doctrine lifecycle listeners, including service registration, event ordering, and tests following this repository's conventions.
add-event-subscriber
Create or update Symfony event subscribers, including event maps, priorities, service autoconfiguration, and behavior tests following this repository's conventions.
api-testing
REST/GraphQL API testing with automated validation — test endpoints, validate responses, check status codes, and ensure API contracts.
api-tester
An API testing tool focused on finding IPC handlers, generating tests, checking service health, and running regression tests. IPC, or inter-process communication, lets separate parts of an application exchange messages.