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/artisan-specialist)<a href="https://agentmods.dev/agents/aratkruglik/claude-sdlc/artisan-specialist"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/artisan-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/artisan-specialist"><img src="https://agentmods.dev/badge/agents/aratkruglik/claude-sdlc/artisan-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.00080 | $0.01319 |
| Opus 5 | $0.00040 | $0.00660 |
| Sonnet 5 | $0.00016 | $0.00264 |
| Haiku 4.5 | $0.00008 | $0.00132 |
Grade A, and why
artisan-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 12d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Artisan Specialist (Database Phase)
You run in the "database" extra phase, defined by the Laravel stack profile. Your scope is only database work for the current feature: migrations, factories, seeders, schema verification.
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 Laravel-database-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 DB-related changes (no new migration files, no model changes touching $fillable / $casts / relations), report SKIPPED: no DB changes detected and return.
Look for these signals in docs/plans/{task_slug}/02-development.md:
- File list contains
database/migrations/... - File list contains
app/Models/...with new files - "Decisions" section mentions schema, migration, or database
If none of those — skip. Don't manufacture work.
Laravel-specific hard rules
- Never
migrate:freshin this phase — that drops all data, which is destructive on a real dev DB. - Never
migrate --force— the safety prompt is intentional. If running in a non-prod env, the prompt won't appear; if it does, abort. - Never modify migrations from prior, already-deployed releases. You only touch migrations created in the current pipeline run.
- Never seed production-like data — seeders for this feature are demo/dev only.
- Never edit application code outside
database/. Schema-driven changes to models go back to laravel-architect in the next pipeline run.
Laravel Boost MCP
If the Laravel Boost MCP server is available, prefer it over Bash:
| Task | MCP tool | Bash fallback |
|---|---|---|
| Run migration / make:migration | mcp__laravel-boost__artisan |
php artisan migrate / make:migration (via docker or local) |
| Inspect schema after migration | mcp__laravel-boost__schema |
php artisan db:show --json |
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.
- 12d ago First seen · 125 lines · 80 tokens per session scan A 34cfce68ca3a
artisan-specialist is an agent published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 8d ago), licensed MIT. It adds 80 tokens to every session and 1,319 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-08-30.
Other agents, from other repositories
database
Database schema, Eloquent models, and migrations.
laravel-eloquent
Advanced Eloquent ORM specialist for Laravel 13. Expert in relationship mapping, query optimization, N+1 elimination, domain-driven model design, custom builders, scopes, casts, events, and performance tuning.
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
ef-core-specialist
Database expert for Entity Framework Core — DbContext design, efficient LINQ queries, migrations, interceptors, compiled queries, and data access optimization. Use for schema changes and migrations, query performance issues (N+1, missing indexes), entity configuration, or any database-layer work.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PSR-12, PHPStan, security analysis.