A research step for a PHP bug or implementation idea that searches earlier discussions and code history. It looks across the PHP internals mailing-list archive, GitHub issues and pull requests, and the php-src commit history.

Use it to check whether a PHP bug or idea has already been discussed, find related issues and pull requests, inspect relevant commits, and add the findings to SPEC.md.

It helps reveal existing explanations, attempted fixes, related changes, and previous decisions before new work begins. Partial results can still be recorded when one source is unavailable.

research — Skill for Claude Code by pronskiy/php-src-developer

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 research

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pronskiy/php-src-developer/research/github.svg)](https://agentmods.dev/skills/pronskiy/php-src-developer/research)

Your own site

<a href="https://agentmods.dev/skills/pronskiy/php-src-developer/research"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/research/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pronskiy/php-src-developer/research"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 176 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,556 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00176	$0.02556
Opus 5.5	$0.00070	$0.01022
Sonnet 5.5	$0.00035	$0.00511
Haiku 4.5	$0.00018	$0.00256

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

Security

Grade A, and why

research scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sS -X POST "https://KSTITII7EC-dsn.algolia.net/1/indexes/v2_emails/query" \

plugins/php-core-developer/skills/research/SKILL.md · 231 lines

How it starts

The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.

research

Generic skill that owns the Research phase in both bug and idea SPEC.md flows. Sweeps four prior-art sources and writes synthesised findings into SPEC.md.

Inputs

SPEC.md in the task directory resolved per _shared/task-dir.md (env var → .current → cwd). Refuse if missing.
gh CLI authenticated (for issue + PR steps).
PHP_SRC_DIR resolvable (for git-log step + task-dir resolution).
Network connectivity (for Algolia + gh steps).

If sub-2 of those are unavailable, the corresponding source-step is marked blocked with the reason and the skill continues with whatever sources do work. Partial findings are still useful — gating differs by flow (soft for bug, hard for idea; see below).

Phase owned

Research.

Position:

SPEC type	Sits between
`bug`	Context → Reproduction
`idea`	Hypothesis & Metric → Survey & Plan

Refuses to run before the upstream phase is done (Context for bug; Hypothesis & Metric for idea).

What it produces

Updated SPEC.md with the Research phase populated:

## Phase: Research — status: done
### Guardrails
- [x] **pre**: upstream phase done (Context for bug; Hypothesis & Metric for idea)
- [x] **post**: at least one source-step done or blocked with reason
### Steps
- [x] **keywords** — <comma-separated list of terms searched>
- [x] **algolia-internals** — <N> hits. <bullets>
- [x] **gh-issues** — <N> hits. <bullets>
- [x] **gh-prs** — <N> hits. <bullets>
- [x] **git-log** — <N> commits. <bullets>

### Notes
<2–4 sentence synthesis across all sources>

Workflow

1. Pre-checks

Resolve task dir per _shared/task-dir.md. SPEC.md exists in the resolved dir. Refuse otherwise — list existing task dirs under $PHP_SRC_DIR/.claude/php-core-dev/ and tell the user how to switch.
SPEC.md has type: bug or type: idea. Refuse otherwise.
Required upstream phase is done:
- bug → Context phase done
- idea → Hypothesis & Metric phase done
- Refuse if not — point at /bug-context or /idea-prototype respectively.
Research phase status check:
- todo or missing → proceed; add the phase skeleton if missing.
- in-progress → resume; only run the source-steps that aren't yet done.
- done → idempotent re-run: refresh the steps' findings (the world may have moved). Backup existing body to a comment block in SPEC.md so the user can see the delta. Don't regress phase status.
- blocked → refuse with reason; tell user to resolve the blocker.
- skipped → refuse with Research phase was deliberately skipped. Reopen by editing SPEC.md if you want to run it.

Read the full file on GitHub · 231 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.

1mo ago First seen · 231 lines · 176 tokens per session scan A f9ab1995063f

Subscribe to this mod's changes

research is a skill published in the GitHub repository pronskiy/php-src-developer (8 stars, last pushed 4mo ago), licensed MIT. It adds 176 tokens to every session and 2,556 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Debugging Research

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

research

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

How it starts

research

Inputs

Phase owned

What it produces

Workflow

1. Pre-checks

What this file has done since we first saw it

Other skills, from other repositories

debug-optimize-lcp

systematic-debugging

log-error-digest

deck-retro

incident-response-incident-response

ci-fixer