agentmods.dev

research

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.

In plain words
What is it for?
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.
Why use it?
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.

Skill for Claude CodeCodex

8 3mo ago A scan 176 tokens original MIT
View the source file 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.

agentmods
npx agentmods add skills/pronskiy/php-src-developer/research
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, Codex.

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. Scan, not verified.
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 $0.00176 $0.02556
Opus 5 $0.00088 $0.01278
Sonnet 5 $0.00035 $0.00511
Haiku 4.5 $0.00018 $0.00256

Measured yesterday against content hash f9ab1995063f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

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

  1. SPEC.md in the task directory resolved per _shared/task-dir.md (env var → .current → cwd). Refuse if missing.
  2. gh CLI authenticated (for issue + PR steps).
  3. PHP_SRC_DIR resolvable (for git-log step + task-dir resolution).
  4. 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.

  1. yesterday 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 3mo ago), licensed MIT. It adds 176 tokens to every session and 2,556 once invoked, about $0.0009 per session on Opus 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.

DebuggingGit and workflowResearch
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens