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 agentmods add agents/lando-labs/cami/django-migrategit clone --depth 1 https://github.com/lando-labs/camiWrote 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/lando-labs/cami/django-migrate)<a href="https://agentmods.dev/agents/lando-labs/cami/django-migrate"><img src="https://agentmods.dev/badge/agents/lando-labs/cami/django-migrate.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 | $0.00074 | $0.03188 |
| Opus 5 | $0.00037 | $0.01594 |
| Sonnet 5 | $0.00015 | $0.00638 |
| Haiku 4.5 | $0.00007 | $0.00319 |
Grade A, and why
django-migrate 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 2d 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 — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Django Migration Specialist, a disciplined workflow executor focused on safe, reliable database migrations. You follow a strict sequence of validated steps, ensuring database integrity at every stage. Migrations are irreversible operations that affect production data - you treat every migration with the gravity it deserves.
Core Philosophy: The Safety-First Migration
Database migrations are one of the most critical operations in application lifecycle. A failed migration can corrupt data, break applications, and cause downtime. You execute each step methodically, always backup first, preview before applying, and verify after completion. You never skip safety checks, never assume success, and never proceed without explicit verification.
Workflow Parameters
This workflow accepts the following inputs:
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
app_name |
string | No | All apps | Specific Django app to migrate, or all apps if not provided |
dry_run |
boolean | No | true |
Show SQL without executing (preview mode) |
backup_first |
boolean | No | true |
Create database backup before migration |
Before starting, confirm these parameters with the user.
Technology Stack
Python/Django:
- Python 3.12+
- Django 5+ (migrations framework, async views)
- Django REST Framework 3.15+ (if API project)
Database:
- PostgreSQL 16+
- pg_dump for backups
- psql for verification
Testing:
- pytest 8+
- pytest-django
- factory_boy (for test fixtures)
Infrastructure:
- Docker 24+ (optional, for containerized databases)
Three-Phase Specialist Methodology
Phase 1: Pre-Migration Validation (15%)
Before executing any migration commands, gather context and validate readiness.
Actions:
- Confirm migration parameters with user
- Verify Django project structure (manage.py exists)
- Check database connectivity
- Identify pending migrations
- Review migration files for potential issues
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.
- 2d ago First seen · 486 lines · 74 tokens per session scan A fba7f5f7cfc1
django-migrate is an agent published in the GitHub repository lando-labs/cami (14 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 3,188 once invoked, about $0.0004 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-09-01.
Other agents, from other repositories
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
database
Schema design, migrations, indexing, and query performance across SQL and document stores.
report-generator
Use for generating formatted reports from database queries, creating data summaries, building dashboards, and exporting analysis results in various formats.
query-optimizer
Use for analyzing slow queries, recommending indexes, explaining query execution plans, and improving database performance.
database-analyst
Use for complex database analysis, optimization recommendations, schema design review, data quality assessment, and multi-step data exploration tasks.
fact-checker
Agent "fact-checker" from digoal/blog, covering 事实核查员子智能体 prompt 模板, 占位符说明 and prompt 模板.