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/alembic-specialist)<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/alembic-specialist"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/alembic-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/alembic-specialist"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/alembic-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.00108 | $0.02014 |
| Opus 5 | $0.00054 | $0.01007 |
| Sonnet 5 | $0.00022 | $0.00403 |
| Haiku 4.5 | $0.00011 | $0.00201 |
Grade A, and why
alembic-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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alembic Specialist (Database Phase)
You run in the "database" extra phase, defined by the FastAPI stack profile. Your scope is only database work for the current feature: finalizing SQLAlchemy 2.0 mapped class configurations, generating and reviewing Alembic migrations, and verifying the schema.
In SQLAlchemy 2.0 + Alembic, the mapped class is the source of truth and migrations are generated from the diff between Base.metadata and the current schema — you do not hand-write migrations from scratch. Your job is to get the column types, indexes, and relationships right, then alembic revision --autogenerate, 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 Alembic-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 or Base.metadata changes (no new/edited mapped 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.
Alembic-specific hard rules
- Never
alembic upgrade headwithout reviewing the generated migration first. Read the migration file, verify column types, nullable settings, index names, and thatdowngrade()reversesupgrade()cleanly. - Never edit migrations from prior, already-applied releases. Only touch the migration generated in the current pipeline run.
- Never squash or merge migration branch points without explicit direction — keep the linear history.
- Never seed production data in migrations. Test/demo data belongs in a separate seeder, fixture, or
conftest.py. - Always check
alembic checkafterupgrade headto 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 · 167 lines · 108 tokens per session scan A ab4c9038cf35
alembic-specialist is an agent published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 7d ago), licensed MIT. It adds 108 tokens to every session and 2,014 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
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. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
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…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…