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 skills/mtnyilmaz/agents/php-developernpx skills add mtnyilmaz/agents --skill php-developergit clone --depth 1 https://github.com/mtnyilmaz/agentsWhat 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.00050 | $0.01421 |
| Opus 5 | $0.00025 | $0.00711 |
| Sonnet 5 | $0.00010 | $0.00284 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
php-developer 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 yesterday.
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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP Developer
Expert in building production-grade PHP applications with Laravel.
Reference Rules
Load these rules for the relevant context:
.agents/layers/language/php/php-patterns.md— PHP strict types, service layer, Eloquent.agents/layers/framework/laravel/laravel-patterns.md— Laravel-specific patterns.agents/layers/concern/backend/api-design.md— REST API design principles.agents/layers/universal/security-baseline.md— security requirements
Project Stack (Modern PHP 2026)
| Tool | Purpose |
|---|---|
| PHP 8.3+ | Language (always latest stable) |
| Laravel 11+ | Framework |
| Eloquent ORM | Database (with SoftDeletes) |
| Laravel Sanctum | API token auth |
| Laravel Horizon | Queue monitoring |
| Pest | Testing (preferred over PHPUnit for new code) |
| PHPStan (level 8+) | Static analysis |
| Laravel Pint | Code formatting (PSR-12) |
| Spatie packages | Permissions, Media, Activity Log, etc. |
Application Structure
/app
/Http
/Controllers/V1 ← thin, delegates to services
/Requests ← Form Request validation
/Resources ← API Resource transformers
/Middleware ← Auth, RBAC, rate limiting
/Services ← all business logic
/Repositories ← DB access (optional, use for complex queries)
/Models ← Eloquent models
/Events ← Domain events
/Listeners ← Event handlers
/Jobs ← Queueable jobs
/Exceptions ← Custom exception classes
/Providers ← Service providers (DI bindings)
/database
/migrations
/factories
/seeders
/tests
/Feature ← HTTP + DB integration tests
/Unit ← Pure service/helper tests
Dependency Injection — Service Provider
// app/Providers/AppServiceProvider.php
public function register(): void
{
$this->app->bind(EmailSenderInterface::class, function () {
return match(config('mail.default_provider')) {
'resend' => new ResendEmailSender(config('services.resend.key')),
'sendgrid' => new SendGridEmailSender(config('services.sendgrid.key')),
default => throw new InvalidArgumentException("Unknown email provider"),
};
});
$this->app->bind(UserRepository::class, EloquentUserRepository::class);
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 195 lines · 50 tokens per session scan A 1afeef7abed7
php-developer is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 1,421 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…