bug-context

bug-context is a skill for Claude Code from pronskiy/php-src-developer. It costs 153 tokens per session (2,417 once invoked), scanned A, original, MIT.

The starting step for working on a PHP bug from a GitHub issue. It fetches the issue and linked changes, summarizes the context, and creates a SPEC.md work record with later bug-fix phases.

In plain words
What is it for?
Use it when beginning work on a PHP GitHub issue to gather its details, record the current source revision and branch, and prepare the bug-fix workflow.
Why use it?
It turns an issue report into a structured task tied to a specific PHP source checkout and code version. This gives reproduction, analysis, implementation, and verification a shared starting point.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the php-core-developer plugin — 9 skills, 1 agent shipped together

Good fit Use it when beginning work on a PHP GitHub issue to gather its details, record the current source revision and branch, and prepare the bug-fix workflow.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pronskiy/php-src-developer/bug-context
Install

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.

Any agent
npx skills add pronskiy/php-src-developer --skill bug-context
Clone the repo
git clone --depth 1 https://github.com/pronskiy/php-src-developer

Made for: Claude Code.

Or install php-core-developer, the plugin that ships this one along with the rest of its 9 skills, 1 agent.

Wrote 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.

agentmods badge for bug-context

README.md
[![agentmods](https://agentmods.dev/badge/skills/pronskiy/php-src-developer/bug-context/github.svg)](https://agentmods.dev/skills/pronskiy/php-src-developer/bug-context)
Your own site
<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.

agentmods 80×15 button for bug-context

Your own site · 80×15
<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>
Per session 153 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,417 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 93ca4548720c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

plugins/php-core-developer/skills/bug-context/SKILL.md · 197 lines

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

  1. Issue identifier (required) — a GitHub issue number (12345), GH-12345, or full URL (https://github.com/php/php-src/issues/12345).
  2. 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.
  3. gh CLI (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 current git rev-parse HEAD of $PHP_SRC_DIR, target_branch: resolved per _shared/branch-detection.md (see step 6 below), created: today's date, status: in-progress.
  • ## Context section 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:

  • 12345
  • GH-12345
  • https://github.com/php/php-src/issues/12345
  • https://github.com/<owner>/<repo>/issues/12345 (rare — non-php/php-src forks)

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

Read the full file on GitHub · 197 lines

Changes

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.

  1. 1mo ago First seen · 197 lines · 153 tokens per session scan A 93ca4548720c

Subscribe to this mod's changes

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.

Related

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

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.

open-metadata/OpenMetadata · 37 tokens

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…

zebbern/claude-code-guide · 71 tokens

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…

asheshgoplani/agent-deck · 86 tokens

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.

rmyndharis/antigravity-skills · 36 tokens

ci-fixer

CI failures - read error, minimal fix, verify.

sipyourdrink-ltd/bernstein · 15 tokens