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 Nevaberry/nevaberry-plugins --skill django-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/django-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/django-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/django-knowledge-patch/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/nevaberry/nevaberry-plugins/django-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/django-knowledge-patch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00008 | $0.02043 |
| Opus 5.5 | $0.00003 | $0.00817 |
| Sonnet 5.5 | $0.00002 | $0.00409 |
| Haiku 4.5 | $0.00001 | $0.00204 |
Grade A, and why
django-knowledge-patch 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 1mo 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django Knowledge Patch
Use this patch when implementing, reviewing, or upgrading Django applications and extensions. Start with compatibility boundaries, then load only the references for the affected subsystem.
Reference index
| Reference | Topics |
|---|---|
| upgrading.md | Runtime and database floors, release status, removals, deprecations, upgrade boundaries |
| orm-and-databases.md | Composite keys, queries, expressions, migrations, backend options and extension APIs |
| http-security-auth.md | CSP, authentication, sessions, redirects, negotiation, URL handling, DRF |
| tasks.md | Task declaration, backends, enqueueing, serialization, transactions, context and results |
| templates-forms-admin.md | Template partials and tags, form rendering, accessibility and admin behavior |
| email-and-feeds.md | Modern mail objects, attachments, keyword-only calls, mail backends and feed stylesheets |
| gis.md | Geometry APIs, spatial operations, GeoIP2, widgets and input limits |
| tooling-testing-serialization.md | Shell imports, commands, testing, pagination, serializers, scaffolding and static files |
Check compatibility before changing code
Read upgrading.md before modifying dependencies or compatibility shims. In particular:
- Match Python, database, GIS library and
asgirefversions to the target Django series. - Confirm whether a development series is actually finalized before choosing it as an upgrade target.
- Search for removed APIs before treating import, argument or extension-hook errors as local bugs.
- Review deprecations against the application's next intended upgrade boundary.
- Test third-party database, field, constraint, mail, middleware, admin, prefetch and widget extensions against their changed contracts.
What ships with it
9 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.
- coverage.json 1.2 KB
- references/email-and-feeds.md 3.2 KB
- references/gis.md 3.0 KB
- references/http-security-auth.md 4.7 KB
- references/orm-and-databases.md 8.1 KB
- references/tasks.md 2.2 KB
- references/templates-forms-admin.md 3.6 KB
- references/tooling-testing-serialization.md 3.3 KB
- references/upgrading.md 7.2 KB
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.
- 1mo ago First seen · 219 lines · 8 tokens per session scan A b4447f082eea
django-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (23 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 2,043 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
add-resource
Scaffold a new MCP resource definition. Use when the user asks to add a resource, expose data via URI, or create a readable endpoint.