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/ldilov/harness-forge/php-engineeringnpx skills add ldilov/harness-forge --skill php-engineeringgit clone --depth 1 https://github.com/ldilov/harness-forgeWhat 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.00013 | $0.00209 |
| Opus 5 | $0.00006 | $0.00105 |
| Sonnet 5 | $0.00003 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
php-engineering 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 28 lines · 13 tokens per session scan A f5fb893354f6
php-engineering is a skill published in the GitHub repository ldilov/harness-forge (4 stars, last pushed 3mo ago), licensed GPL-3.0. It adds 13 tokens to every session and 209 once invoked, about $0.0001 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
loopplane
Initialize and run a durable, plan-driven agent workflow inside any project using external CLI coding agents.
review-pr
Review gate for one agentdeck PR before merge. Five phases (claims, attack, craft, scope, verdict) plus an optional harvest; BLOCK/DISCUSS/DEFER/NIT findings; a 300-word verdict ending in a greppable marker. Use before merging any agentdeck PR.
ship-pr
Implement one agentdeck GitHub issue end to end as a PR: design in the PR body before code, code that matches its analog, self-review that catches the path no test exercises, then the merge gate. Five stages (understand, design, implement, self-review, gate). Use when implementing an agentdeck issue as deck-dev.
milestone-retro
Evaluate the harness after a milestone closes: which CI gates fired, whether the slop guards caught anything, how the dev and review agents performed, and whether the PRs were well shaped. Judges the machinery, not the product. Use when a milestone is finished and before the release is tagged.
ship-issue
Run one agentdeck issue through the full pipeline: brief the user, deck-dev implements it, deck-reviewer gates it, findings get fixed, PR merges to dev, board updated.
open-issue
File a well-formed agentdeck GitHub issue in the repo's house style (Problem / Proposed shape / Notes / Done when).