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 library-authorgit 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/library-author)<a href="https://agentmods.dev/skills/hmj1026/dhpk/library-author"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/library-author/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/library-author"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/library-author.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.00068 | $0.00562 |
| Opus 5.5 | $0.00027 | $0.00225 |
| Sonnet 5.5 | $0.00014 | $0.00112 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
library-author 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.
What it actually says
Library author
Use a natural-language library task or an explicit mode followed by its inputs.
- Select the mode below from the requested deliverable. An explicit mode wins; clarify a genuinely ambiguous deliverable before loading a procedure.
- Identify the consumer package, declared PHP/framework/dependency range, and existing matrix from local metadata. Preserve each procedure's version inference; do not invent pins where consumer evidence is missing.
- Load only the selected mode procedure. Load its named sibling reference only for the relevant branch. Complete its input, authority, and verification gates.
- Return that mode's output with actual check results and remaining gaps. A release plan does not authorize publication, tags, or external changes.
| Mode | Task and input | Procedure | Output |
|---|---|---|---|
| author | Provider, facade, publishing or discovery design; supported range | author | Authoring decision or package design with compatibility gates |
| testbench | Multi-major Laravel matrix; package dependency metadata | testbench | Per-cell CI matrix, TestCase, database and discovery evidence |
| composer | Public API, Composer manifest, dependency floor or release contract | composer | Semver verdict, audited manifest or release gate |
| polyfill-audit | File, symbol or all version guards; declared and executed matrices | polyfill-audit | Branch enumeration, matrix gaps and asymmetric-edit report |
| suite-map | Edited paths and actual phpunit.xml suite directories | suite-map | Selected suites, commands and boundary warnings |
| cell-onboard | Proposed pinned runtime/dependency tuple and current workflow | cell-onboard | Composer, workflow, polyfill, Testbench and focused-test cell plan |
Distinct deliverables retain distinct contracts. A task spanning modes may run them in a stated sequence, retaining each mode's evidence and authority.
This relocatable skill is separate from the consumer content module
modules/library-author/. Its mode references are resources, not peer skills.
What ships with it
11 files 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.
- agents/openai.yaml 249 B
- distribution.yaml 3.3 KB
- references/author.md 2.6 KB
- references/authoring-patterns.md 4.1 KB
- references/cell-onboard.md 7.3 KB
- references/composer.md 2.7 KB
- references/package-contracts.md 3.9 KB
- references/polyfill-audit.md 7.3 KB
- references/suite-map.md 4.0 KB
- references/testbench-recipes.md 3.6 KB
- references/testbench.md 2.5 KB
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 · 38 lines · 68 tokens per session scan A 5e5f16e0a441
library-author is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 562 once invoked, about $0.0003 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-10-16.
Other skills, from other repositories
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
php-testing
Use when writing/configuring tests on a non-Laravel PHP project — PHPUnit vs Pest. Do NOT use for Laravel test helpers or quality tooling (php-quality-tooling).
Test Scaffold (Laravel/PHPUnit)
Generate PHP/Laravel (PHPUnit) test skeletons from specifications.
php-quality
A PHP quality-check workflow using PHPStan, Pint, PHPUnit, Pest, or Laravel's test command. It checks code behavior, types, style, and formatting.
craft-test-suite
Crafting a test suite. Zero to green in 60 seconds.
craft-test-factory
Crafting Test Factories. Beyond Laravel defaults.