django-middleware-for-request-response

django-middleware-for-request-response is a cursor rule for Cursor from claire-gong-18/awesome-cursorrules. It costs 49 tokens per session, scanned A, a copy of django-middleware-for-request-response, CC0-1.0.

A project rule for using Django middleware, code that can process requests before a view and responses after it.

In plain words
What is it for?
It helps add shared request and response processing to a Django application.
Why use it?
It provides one consistent place for actions that should apply across many requests and responses.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit It helps add shared request and response processing to a Django application.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/claire-gong-18/awesome-cursorrules/django-middleware-for-request-response
Install

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.

Clone the repo
git clone --depth 1 https://github.com/claire-gong-18/awesome-cursorrules

Made for: Cursor.

Wrote 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.

agentmods badge for django-middleware-for-request-response

README.md
[![agentmods](https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/django-middleware-for-request-response/github.svg)](https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/django-middleware-for-request-response)
Your own site
<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/django-middleware-for-request-response"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/django-middleware-for-request-response/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.

agentmods 80×15 button for django-middleware-for-request-response

Your own site · 80×15
<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/django-middleware-for-request-response"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/django-middleware-for-request-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 This file is loaded in full into every session.
When invoked 49 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.00049
Opus 5 $0.00024 $0.00024
Sonnet 5 $0.00010 $0.00010
Haiku 4.5 $0.00005 $0.00005

Measured 5d ago against content hash ad4c312d6447, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

django-middleware-for-request-response 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 5d 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.

Origin

This is a copy

100% identical to django-middleware-for-request-response — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

rules/htmx-django-cursorrules-prompt-file/django-middleware-for-request-response.mdc · 5 lines

What it actually says

  • Utilize Django's middleware for request/response processing
Changes

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.

  1. 5d ago First seen · 5 lines · 49 tokens per session scan A ad4c312d6447

Subscribe to this mod's changes

django-middleware-for-request-response is a cursor rule published in the GitHub repository claire-gong-18/awesome-cursorrules (0 stars, last pushed 1y ago), licensed CC0-1.0. It adds 49 tokens to every session, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to django-middleware-for-request-response, differing in 0 lines, and is treated as a copy.