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 pronskiy/php-src-developer --skill bug-verifygit clone --depth 1 https://github.com/pronskiy/php-src-developerWrote 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/pronskiy/php-src-developer/bug-verify)<a href="https://agentmods.dev/skills/pronskiy/php-src-developer/bug-verify"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/bug-verify/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/pronskiy/php-src-developer/bug-verify"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/bug-verify.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.00104 | $0.02639 |
| Opus 5.5 | $0.00042 | $0.01056 |
| Sonnet 5.5 | $0.00021 | $0.00528 |
| Haiku 4.5 | $0.00010 | $0.00264 |
Grade A, and why
bug-verify 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bug-verify
Fourth and last step of the bug-fix flow. Owns the Verification phase. Confirms the fix doesn't regress nearby tests and doesn't introduce new compiler warnings.
Inputs
- SPEC.md in the task directory resolved per
_shared/task-dir.md(env var →.current→ cwd),type: bug, Implementation phasedone. $PHP_SRC_DIRwith the post-fixsapi/cli/phpbuilt.
What it produces
- Updated SPEC.md: Verification phase
done(orblockedwith reasons), top-levelstatus: done. - A summary suitable for the user's commit / PR description.
Phase owned
Verification.
Steps this skill adds (some are optional):
related-tests—make TESTS=<related-dir> testorrun-tests.php <related-dir>passes.dependents-tests— extensions that link against (or#includeheaders from) the changed translation unit pass their own test directories. Always added by default; one sub-step per dependent extension that triggers any new failure. Catches the cross-extension regression case where e.g. a change inext/datebreaksext/spl.warnings-clean— no new compiler warnings versusphp_src_ref(the SHA recorded in SPEC.md frontmatter).full-test(optional) —make test; only added if the user explicitly asks.valgrind/asan(optional) — only for memory-sensitive fixes; only on user request.
Workflow
1. Pre-guardrails
- SPEC.md
type: bug, Implementation phasedone. Refuse otherwise. - The new
.phptfrom Reproduction is recorded.
2. Choose the related test directory
From the Implementation steps (impl-N) and the Reproduction test path, pick the nearest meaningful test directory:
| Changed file | Related test dir |
|---|---|
ext/<name>/... |
ext/<name>/tests/ |
Zend/... |
Zend/tests/ |
main/streams/... |
tests/streams/ |
sapi/<name>/... |
sapi/<name>/tests/ |
If the change touches multiple subsystems, run each. Add a related-tests step per directory.
3. Run related tests
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 · 214 lines · 104 tokens per session scan A 394656cda68d
bug-verify is a skill published in the GitHub repository pronskiy/php-src-developer (8 stars, last pushed 4mo ago), licensed MIT. It adds 104 tokens to every session and 2,639 once invoked, about $0.0004 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
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.