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 skills add hmj1026/dhpk --skill dhpk-yii1-php56-developmentgit clone --depth 1 https://github.com/hmj1026/dhpkWrote 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/skills/hmj1026/dhpk/dhpk-yii1-php56-development)<a href="https://agentmods.dev/skills/hmj1026/dhpk/dhpk-yii1-php56-development"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-yii1-php56-development/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/skills/hmj1026/dhpk/dhpk-yii1-php56-development"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-yii1-php56-development.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.00071 | $0.02064 |
| Opus 5 | $0.00036 | $0.01032 |
| Sonnet 5 | $0.00014 | $0.00413 |
| Haiku 4.5 | $0.00007 | $0.00206 |
Grade A, and why
dhpk-yii1-php56-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 7d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Php56 Yii Dev
Overview
Use this skill to work on generic Yii 1.x backend tasks in legacy PHP 5.6 environments without introducing syntax or patterns that block a later PHP 7 upgrade. Keep the workflow small: refresh framework knowledge through Context7 when needed, design with pragmatic DDD boundaries, drive changes with tests, then implement and verify.
When NOT to Use
- Frontend-only work, documentation-only edits, or non-PHP stacks.
- The workflow still needs classification or gate decisions — route to
$flow-guidefirst, then return here for implementation. - The bug's root cause is unknown — route to
$code-tracefirst, then return here for the PHP 5.6-safe fix. - Modern PHP 7+/PHPUnit 6+ greenfield code with no PHP 5.6 runtime constraint.
Core Rules
- Treat PHP 5.6 runtime compatibility as a hard constraint.
- Prefer code that still works after upgrading to PHP 7.x.
- Keep Controllers thin and move business rules into Application Service, Domain Service, Entity, or Value Object.
- Use TDD by default: write or identify a failing test before changing behavior.
- Use Context7 as the knowledge source for language, framework, testing, and security questions. State when a recommendation is an inference from the sources.
- If the task is simple CRUD with no real domain complexity, keep the design light and do not force ceremony.
Critical Never List
- Never introduce PHP 7+ syntax or PHPUnit 6+ APIs into code or tests that must run on PHP 5.6 and PHPUnit 5.7.
- Never leave business rules, validation rules, or SQL-heavy orchestration in a Controller when a Service, Domain object, or Repository boundary would make the change clearer.
- Never trust mass assignment, request filters, sorting input, table names, or column names without scenario checks or allow-list validation.
- Never concatenate untrusted input into SQL, and never assume
queryRow()orqueryScalar()returnsnullon no result. - Never use
strcmp()to verify MySQL string ordering underutf8_unicode_ci; usestrcasecmp()for ordering assertions. - Never pretend a risky legacy path is covered when it is not. Write a characterization test, isolate a smaller seam, or call out the coverage gap explicitly.
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.
- 7d ago First seen · 195 lines · 71 tokens per session scan A 9f41452de9d8
dhpk-yii1-php56-development is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 2,064 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-09-05.
Other skills, from other repositories
craftcms
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing…
php-ecosystem-reference
Use when picking a non-Laravel PHP tool — Symfony components, API Platform, or Slim — and routing to implementation. Do NOT use for Laravel (laravel-expert).
php-http-psr
Use when building framework-agnostic PHP HTTP code — PSR-7/15/17/18 messages, middleware, factories, clients. Do NOT use for Laravel HTTP or Symfony HttpFoundation (not PSR-7).
php-laravel
Modern PHP 8.2+ and Laravel patterns: architecture, Eloquent, queues, Pest testing. Use when asked to "write PHP", "build a Laravel app", "fix Eloquent query", "add a queue job", "write a Pest test", or mentions PHP, Laravel, Eloquent, Blade, artisan, or migrations.
ia-php-laravel
Modern PHP 8.4 and Laravel patterns: architecture, Eloquent, migrations, queues, testing. Use when working with Laravel, Eloquent, Blade, artisan, or building/testing a framework-based PHP app. Not for php-src internals, standalone PHP libraries, or general PHP language discussion.
symfony:interfaces-and-autowiring
Master Symfony Dependency Injection with autowiring.