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 maludb-ed/htmx-php-builder --skill php-patternsgit clone --depth 1 https://github.com/maludb-ed/htmx-php-builderWrote 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/maludb-ed/htmx-php-builder/php-patterns)<a href="https://agentmods.dev/skills/maludb-ed/htmx-php-builder/php-patterns"><img src="https://agentmods.dev/badge/skills/maludb-ed/htmx-php-builder/php-patterns/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/maludb-ed/htmx-php-builder/php-patterns"><img src="https://agentmods.dev/badge/skills/maludb-ed/htmx-php-builder/php-patterns.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.00058 | $0.01388 |
| Opus 5.5 | $0.00023 | $0.00555 |
| Sonnet 5.5 | $0.00012 | $0.00278 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
php-patterns 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 1mo 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP Design Pattern
Every application uses the feature-oriented Page Controller pattern defined in references/pattern-guide.md — read it before writing PHP. This SKILL.md is the enforcement summary plus the plugin-integration rules.
The pattern in one view
| Responsibility | Implementation |
|---|---|
| Controller | Small procedural PHP endpoint under /var/www/html/{feature}/ (the Apache DocumentRoot on Ubuntu 24.04) |
| Data access | Procedural functions taking PDO as first param, in app/features/{feature}/queries.php |
| Full-page view | app/views/{feature}/page.php (wrapped by app/views/layout.php) |
| Fragment view | app/views/{feature}/partials/*.php |
| Infrastructure | app/bootstrap.php, app/db.php, app/http.php |
Vertical slices: one feature = one /var/www/html/{feature}/ endpoint set + one /var/www/app/features/{feature}/queries.php + one /var/www/app/views/{feature}/ view set. The web root is /var/www/html (Apache's default DocumentRoot on Ubuntu 24.04) — build the application there, not in a public/ directory; app/ and config/ sit beside html/ under /var/www/, outside the DocumentRoot, and must never be placed inside it. No classes for controllers, repositories, services, DTOs, or entities — extract shared procedural helpers only when duplication becomes substantial.
Controller sequence (every endpoint)
bootstrap → authenticate/authorize → read input → validate
→ query functions → log activity → render page or partial
- State-changing endpoints start with
require_post(); verify_csrf();. - Controllers pass explicit values to query functions; query functions never see
$_GET/$_POST, HTMX, HTTP codes, or templates. - Views receive data, never fetch it. Dependency direction is always endpoint → queries → PDO → PostgreSQL, and endpoint → template.
- Log activity (the plugin's activity-log/MaluDB requirement) in the controller after a successful action — inside the same transaction when the action writes (see the transaction example in the guide).
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.
- 1mo ago First seen · 64 lines · 58 tokens per session scan A 30803207dbee
php-patterns is a skill published in the GitHub repository maludb-ed/htmx-php-builder (9 stars, last pushed 14d ago), licensed MIT. It adds 58 tokens to every session and 1,388 once invoked, about $0.0002 per session on Opus 5.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
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
create-powergrid-plugin
Create a complete PowerGrid plugin from scratch, including PHP class, Column macro, Blade view, Alpine.js component, and registration.
owl-admin-devtools-generator
A development guide for Owl Admin, a Laravel-based administration system, covering its code generator, API templates, relationships, and visual pages.
llamaindex-development
Expert guidance for LlamaIndex development including RAG applications, vector stores, document processing, query engines, and building production AI applications.
laravel-idioms
Laravel framework patterns: Eloquent ORM relationships, N+1 query prevention, Form Request validation, Service layer architecture, and Pest/PHPUnit testing. Use when building or reviewing Laravel web apps and APIs. Pair with php-idioms.
php-laravel
Build and upgrade PHP/Laravel applications with validated requests, policy authorization and reliable jobs/data access. Use when implementing Laravel routes, Eloquent models or queues; preserve existing project conventions and runtime compatibility.