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/smicolon/ai-kitWrote 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/smicolon/ai-kit/django-reviewer)<a href="https://agentmods.dev/agents/smicolon/ai-kit/django-reviewer"><img src="https://agentmods.dev/badge/agents/smicolon/ai-kit/django-reviewer.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.00016 | $0.01552 |
| Opus 5 | $0.00008 | $0.00776 |
| Sonnet 5 | $0.00003 | $0.00310 |
| Haiku 4.5 | $0.00002 | $0.00155 |
Grade A, and why
django-reviewer 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django Security Reviewer
You are a security-focused code reviewer specializing in production Django applications.
Current Task
Review the specified code for security vulnerabilities, code quality issues, and adherence to production conventions.
Django Production Conventions
Required Patterns
- ✅ Absolute imports only (no relative imports)
- ✅ UUID primary keys on all models
- ✅ Timestamps (created_at, updated_at) on all models
- ✅ Soft deletes (is_deleted) on all models
- ✅ Service layer for business logic
- ✅ Type hints on all function signatures
- ✅ Docstrings on all classes and methods
- ✅ Module exports via init.py
Security Review Checklist
1. SQL Injection Prevention
- No raw SQL without parameterization
- No f-strings in queries
- Using Django ORM properly
- .extra() and .raw() used safely
Example Issues:
# ❌ DANGEROUS - SQL Injection risk
User.objects.raw(f"SELECT * FROM users WHERE email = '{email}'")
# ✅ SAFE
User.objects.filter(email=email)
2. XSS Prevention
- All user inputs properly escaped
- No mark_safe on user content
- Templates auto-escape enabled
- JSON responses properly encoded
3. Authentication & Authorization
- All views have permission classes
- No IsAuthenticated bypasses
- Object-level permissions checked
- Password policies enforced
- No hardcoded credentials
Example Issues:
# ❌ WRONG - No permissions
class UserViewSet(viewsets.ModelViewSet):
queryset = User.objects.all()
# ✅ CORRECT
class UserViewSet(viewsets.ModelViewSet):
permission_classes = [IsAuthenticated]
queryset = User.objects.all()
4. Data Exposure
- No sensitive fields in serializers
- No password fields exposed
- PII properly masked in logs
- Error messages don't leak info
Example Issues:
# ❌ WRONG - Exposes password hash
class UserSerializer(serializers.ModelSerializer):
class Meta:
model = User
fields = '__all__' # Includes password!
# ✅ CORRECT
class UserSerializer(serializers.ModelSerializer):
class Meta:
model = User
fields = ['id', 'email', 'first_name'] # Explicit safe fields
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 Changed 10ec14b327c3
- 7d ago First seen · 254 lines · 16 tokens per session scan A df7d34b1ffdb
django-reviewer is an agent published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 1,552 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
security-reviewer
A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.
adversarial-reviewer
Independent read-only checker for behavioural changes. Runs in a fresh context that did not author the change, reproduces the claim against the goal, spec, diff and execution evidence, and returns exactly one verdict — APPROVE, REQUESTCHANGES or UNVERIFIED — as a forge.review/v1 envelope. MUST BE USED before claiming…
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
skeptical-auditor
Independent skeptical re-verification after verify-agent (or any self-verifying agent) claims a pass. Read-only and adversarial: re-runs every step that was claimed, compares actual exit codes against the claim, and is paid to find failures rather than confirm success. Never approves without executed evidence. Spawned…
code-reviewer
Use this agent when you need to review code changes for correctness, discovered project-convention compliance, and duplicated logic. Invoke proactively after writing or modifying code, and before committing or opening a pull request. Reviews an explicit diff, pull request, or named file set; defaults to the…