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-dj-rest-authgit 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-dj-rest-auth)<a href="https://agentmods.dev/skills/wemake-services/django-modern-rest/dmr-from-dj-rest-auth"><img src="https://agentmods.dev/badge/skills/wemake-services/django-modern-rest/dmr-from-dj-rest-auth/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-dj-rest-auth"><img src="https://agentmods.dev/badge/skills/wemake-services/django-modern-rest/dmr-from-dj-rest-auth.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.00067 | $0.02212 |
| Opus 5.5 | $0.00027 | $0.00885 |
| Sonnet 5.5 | $0.00013 | $0.00442 |
| Haiku 4.5 | $0.00007 | $0.00221 |
Grade A, and why
dmr-from-dj-rest-auth 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DMR from dj-rest-auth
Overview
Migrate a dj-rest-auth installation to django-modern-rest.
Required docs (always reference first):
- DMR LLM docs: https://django-modern-rest.readthedocs.io/llms.txt
- dj-rest-auth docs: https://dj-rest-auth.readthedocs.io/en/latest/
- allauth headless docs: https://docs.allauth.org/en/latest/headless/index.html
- Local map: references/dj-rest-auth-to-dmr-map.md
Read This First
This migration is not shaped like $dmr-from-drf.
dj-rest-auth is a DRF layer on top of django-allauth. We do not
reimplement account management. django-allauth keeps owning registration,
email verification, password reset, social login, MFA, and passkeys through
its headless mode, and django-modern-rest owns your own API surface plus
the auth classes that read allauth's credentials.
Three consequences the user must accept before any code is written:
- Endpoint paths change. allauth headless serves its own
/_allauth/{client}/v1/...routes. Strict path parity is not a goal and usually not achievable. - Request and response payloads change. allauth has its own envelope
(
status,data,meta) and its own error format. - Every API client must be updated. Treat this as a coordinated frontend + backend migration, not a drop-in backend swap.
If the user cannot change clients, stop and say so. A compatibility shim
that re-serves dj-rest-auth paths and payloads is possible but is a
long-lived maintenance burden. Do not build one silently.
Migration Policy
- Default mode:
behavioral parity, nottransport parity. The same things must be possible; the wire format may differ. - Preserve by default: which flows exist, who can call them, what security properties they have, what lands in the database.
- Every path, payload, or status-code change is
approved driftand must be listed explicitly. Never let a drift pass unlisted just because the endpoint "still works". - Never weaken a security property to make a client's life easier. Call it out and let the user decide.
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 · 223 lines · 67 tokens per session scan A a1a49bcdde21
dmr-from-dj-rest-auth is a skill published in the GitHub repository wemake-services/django-modern-rest (1,519 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 2,212 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-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
horse-database-pooling
Guide for setting up thread-safe database connection pooling (FireDAC / UniDAC) in multithreaded Horse applications.
horse-request-response
Guide to interacting with THorseRequest (body, query, params, headers) and THorseResponse (Send, Status, ContentType).
horse-dependency-injection
Guide for managing request-scoped contextual services and IoC (dependency injection) in Delphi and Lazarus.
horse-mvc-architecture
Guide for structuring corporate Horse applications using Clean MVC (Model-View-Controller) principles and decoupling HTTP layers from business logic.
horse-app-structure
Guide for setting up Horse applications, bootstrap program (.dpr), basic console initialization, and registering modules.