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/maludb-ed/htmx-php-builder/php-patternsnpx skills add maludb-ed/htmx-php-builder --skill php-patternsgit clone --depth 1 https://github.com/maludb-ed/htmx-php-builderWhat 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.00058 | $0.01388 |
| Opus 5 | $0.00029 | $0.00694 |
| Sonnet 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 2d 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.
- 2d 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 (8 stars, last pushed 26d ago), licensed MIT. It adds 58 tokens to every session and 1,388 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…