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-contextgit 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-context)<a href="https://agentmods.dev/skills/pronskiy/php-src-developer/bug-context"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/bug-context/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-context"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/bug-context.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.00153 | $0.02417 |
| Opus 5.5 | $0.00061 | $0.00967 |
| Sonnet 5.5 | $0.00031 | $0.00483 |
| Haiku 4.5 | $0.00015 | $0.00242 |
Grade A, and why
bug-context 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bug-context
Entry point of the php-src bug-fix flow. Pulls the GitHub issue, synthesises it, and writes the Context phase of SPEC.md.
Inputs
- Issue identifier (required) — a GitHub issue number (
12345),GH-12345, or full URL (https://github.com/php/php-src/issues/12345). PHP_SRC_DIR(required) — resolved per_shared/php-src-detection.md(auto-detect cwd inside checkout, or honour the env var override). Refuse if neither path resolves.ghCLI (required) — must be authenticated (gh auth status). If unauthenticated, stop and tell the user.
What it produces
SPEC.md in the task directory (resolved per _shared/task-dir.md; default $PHP_SRC_DIR/.claude/php-core-dev/gh-<N>/SPEC.md) with:
- Frontmatter:
type: bug,linked:set to the GH issue URL,php_src_ref:set to the currentgit rev-parse HEADof$PHP_SRC_DIR,target_branch:resolved per_shared/branch-detection.md(see step 6 below),created:today's date,status: in-progress. ## Contextsection with a synthesised problem statement.- Phase skeletons (Reproduction, Analysis & Plan, Implementation, Verification) — all
status: todo, with their guardrails pre-declared. - Empty
## Open Questions. - A first Progress Log entry.
Workflow
1. Resolve PHP_SRC_DIR and validate environment
Resolve PHP_SRC_DIR using the algorithm in _shared/php-src-detection.md (env-var override or walk-up from $PWD). If neither path resolves, refuse with the detection doc's error message — do not guess.
gh auth status >/dev/null 2>&1 || { echo "gh CLI not authenticated. Run: gh auth login"; exit 1; }
2. Resolve issue identifier
Accept any of:
12345GH-12345https://github.com/php/php-src/issues/12345https://github.com/<owner>/<repo>/issues/12345(rare — non-php/php-srcforks)
Default repo is php/php-src when only a number is given.
3. Fetch issue data
gh issue view <N> --repo php/php-src --json number,title,body,labels,state,url,comments,createdAt,author
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 · 197 lines · 153 tokens per session scan A 93ca4548720c
bug-context is a skill published in the GitHub repository pronskiy/php-src-developer (8 stars, last pushed 4mo ago), licensed MIT. It adds 153 tokens to every session and 2,417 once invoked, about $0.0006 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.