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/dallay/agents-skills/php-developmentnpx skills add dallay/agents-skills --skill php-developmentgit clone --depth 1 https://github.com/dallay/agents-skillsWhat 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.00045 | $0.02695 |
| Opus 5 | $0.00023 | $0.01347 |
| Sonnet 5 | $0.00009 | $0.00539 |
| Haiku 4.5 | $0.00005 | $0.00269 |
Grade A, and why
php-development 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 — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP Development
Production patterns for modern PHP (8.x+), covering Composer, PSR standards, type safety, testing with PHPUnit, and architectural best practices.
When to Use This Skill
- Building or structuring a PHP application
- Working with Composer for dependency management
- Following PSR standards (autoloading, coding style)
- Using PHP 8.x features (attributes, enums, fibers, typed properties)
- Writing tests with PHPUnit
- Applying clean architecture in PHP projects
Core Concepts
1. Project Layout (PSR-4)
myapp/
├── src/
│ ├── Controller/
│ │ └── UserController.php
│ ├── Service/
│ │ └── UserService.php
│ ├── Repository/
│ │ └── UserRepository.php
│ ├── Entity/
│ │ └── User.php
│ ├── Exception/
│ │ ├── AppException.php
│ │ └── NotFoundException.php
│ └── ValueObject/
│ └── Email.php
├── tests/
│ ├── Unit/
│ │ └── Service/
│ │ └── UserServiceTest.php
│ └── Integration/
│ └── Repository/
│ └── UserRepositoryTest.php
├── config/
├── public/
│ └── index.php
├── composer.json
├── phpunit.xml
└── README.md
2. Key Standards
| Standard | Purpose |
|---|---|
| PSR-4 | Autoloading: namespace ↔ directory map |
| PSR-12 | Extended coding style (superseded by PER-CS) |
| PSR-7 | HTTP message interfaces |
| PSR-11 | Container interface (DI) |
| PSR-3 | Logger interface |
Quick Start
# Initialize project
composer init
# Install dependencies
composer require guzzlehttp/guzzle
composer require --dev phpunit/phpunit phpstan/phpstan
# Autoload (PSR-4 in composer.json)
composer dump-autoload
# Run tests
./vendor/bin/phpunit
# Static analysis
./vendor/bin/phpstan analyse src --level=max
# Code style fix
./vendor/bin/php-cs-fixer fix src
{
"autoload": {
"psr-4": {
"App\\": "src/"
}
},
"autoload-dev": {
"psr-4": {
"App\\Tests\\": "tests/"
}
}
}
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 · 466 lines · 45 tokens per session scan A d7090dad3c94
php-development is a skill published in the GitHub repository dallay/agents-skills (2 stars, last pushed 9d ago), licensed MIT. It adds 45 tokens to every session and 2,695 once invoked, about $0.0002 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…