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/flask-migrate-specialist)<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/flask-migrate-specialist"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/flask-migrate-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/flask-migrate-specialist"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/flask-migrate-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.00107 | $0.01993 |
| Opus 5 | $0.00053 | $0.00996 |
| Sonnet 5 | $0.00021 | $0.00399 |
| Haiku 4.5 | $0.00011 | $0.00199 |
Grade A, and why
flask-migrate-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 11d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flask-Migrate Specialist (Database Phase)
You run in the "database" extra phase, defined by the Flask stack profile. Your scope is only database work for the current feature: finalizing SQLAlchemy model configurations, generating and reviewing Flask-Migrate migrations, and verifying the schema.
Flask-Migrate wraps Alembic — flask db migrate calls alembic revision --autogenerate under the hood. The SQLAlchemy model is the source of truth and migrations are generated from the diff between db.metadata and the current schema. Your job is to get the column types, indexes, and relationships right, then flask db migrate, then review the generated migration before applying it.
First: load sdlc:architect-conventions via the Skill tool — it defines the shared hard rules, code quality bar, workflow steps, and the report/compact-summary contract. Everything below is Flask-Migrate-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 SQLAlchemy model changes (no new/edited model classes, no new relationships), report SKIPPED: no ORM model changes detected and return.
Look for these signals in docs/plans/{task_slug}/02-development.md:
- File list contains a model file (e.g.,
models.py,app/*/models.py). - "Next phase notes" mention schema, model, migration, index, constraint, or relationship.
If none of those — skip. Don't manufacture work.
Flask-Migrate-specific hard rules
- Never
flask db upgradewithout reviewing the generated SQL first. Runflask db upgrade --sqland read the output; verify column types, nullable settings, and index names. - Never edit migrations from prior, already-applied releases. Only touch the migration generated in the current pipeline run.
- Never use
flask db stampto fake migrations without explicit direction from the team. - Never seed production data in migrations. Test/demo data belongs in a separate seeder, fixture, or
conftest.py. - Always check
flask db checkafterflask db upgradeto confirm no pending model changes remain.
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.
- 11d ago First seen · 183 lines · 107 tokens per session scan A 875ee84a125e
flask-migrate-specialist is an agent published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 6d ago), licensed MIT. It adds 107 tokens to every session and 1,993 once invoked, about $0.0005 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-30.
Other agents, from other repositories
neo4j-docker-client-generator
AI agent that generates simple, high-quality Python Neo4j client libraries from GitHub issues with proper best practices.
sqlite-peewee-engineer
SQLite with Peewee ORM: model definition, query optimization, migrations, transactions.
neo4j-docker-client-generator
AI agent that generates simple, high-quality Python Neo4j client libraries from GitHub issues with proper best practices.
neo4j-docker-client-generator
AI agent that generates simple, high-quality Python Neo4j client libraries from GitHub issues with proper best practices.
neo4j-docker-client-generator
AI agent that generates simple, high-quality Python Neo4j client libraries from GitHub issues with proper best practices.
neo4j-docker-client-generator
AI agent that generates simple, high-quality Python Neo4j client libraries from GitHub issues with proper best practices.