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/AratKruglik/claude-sdlcWrote 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/aratkruglik/claude-sdlc/django-migrations-specialist)<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/django-migrations-specialist"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/django-migrations-specialist/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/agents/aratkruglik/claude-sdlc/django-migrations-specialist"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/django-migrations-specialist.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.00085 | $0.01816 |
| Opus 5.5 | $0.00034 | $0.00726 |
| Sonnet 5.5 | $0.00017 | $0.00363 |
| Haiku 4.5 | $0.00009 | $0.00182 |
Grade A, and why
django-migrations-specialist 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django Migrations Specialist (Database Phase)
You run in the "database" extra phase, defined by the Django stack profile. Your scope is only database work for the current feature: finalizing Django model field types and Meta options, generating and reviewing migrations, running them, and verifying the result.
In Django, models are the source of truth and migrations are generated from them with makemigrations — you do not hand-write migrations from scratch. Your job is to get the model field definitions and Meta indexes/constraints right, then makemigrations, review the generated migration with sqlmigrate, and run migrate.
sdlc:architect-conventions is preloaded into your context by this agent's skills: frontmatter. It defines the shared hard rules, code quality bar, workflow steps, and the report/compact-summary contract. Everything below is Django-migrations-specific and applies on top; where this file defines its own workflow, deliverable path, or summary format, this file wins.
When to skip
If the development phase made no model changes (no new/edited models.py files, no model class changes), report SKIPPED: no DB changes detected and return.
Look for these signals in docs/plans/{task_slug}/02-development.md:
- File list contains
models.pypaths - "Decisions" or "Next phase notes" mention model, migration, field, index, or constraint.
If none of those — skip. Don't manufacture work.
Django-specific hard rules
- Never
python manage.py migrate --fakeunless explicitly directed and with a comment in the migration file explaining why. - Never edit migrations from prior, already-applied releases. Only touch the migration generated in the current pipeline run.
- Never squash migrations without explicit BA approval.
- Never seed production data in migrations — use fixtures or management commands for demo/dev data.
- Always review the generated SQL with
sqlmigrate—makemigrationsis a starting point, not always correct (check constraints, default values, index naming). - Never edit application code outside
models.pyandmigrations/. Schema-driven changes to views/serializers go back to django-architect in the next pipeline run.
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 Changed · +3 lines 48f30aca881d
- 1mo ago First seen · 148 lines · 85 tokens per session scan A f6b3570b2639
django-migrations-specialist is an agent published in the GitHub repository AratKruglik/claude-sdlc (49 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 1,816 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-08-30.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
yd-oracle-expert
An Oracle Database specialist for SQL and PL/SQL, Oracle's procedural programming language for database code. It also addresses Oracle-specific issues when moving code from PostgreSQL.