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 idea-prototypegit 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/idea-prototype)<a href="https://agentmods.dev/skills/pronskiy/php-src-developer/idea-prototype"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/idea-prototype/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/idea-prototype"><img src="https://agentmods.dev/badge/skills/pronskiy/php-src-developer/idea-prototype.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.00129 | $0.05047 |
| Opus 5.5 | $0.00052 | $0.02019 |
| Sonnet 5.5 | $0.00026 | $0.01009 |
| Haiku 4.5 | $0.00013 | $0.00505 |
Grade A, and why
idea-prototype 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
idea-prototype
Single skill that drives a php-src idea prototype from a one-liner to a verdict. Like the bug flow, it's phased and resumable; unlike the bug flow, one skill owns all phases. Each invocation advances one phase forward (or resumes a blocked phase).
Inputs
- A one-line hypothesis (required on first run only) — e.g. "caching common
zend_stringparameter names could speed up function calls", "adding pattern syntax X would simplify Y", "replacing the linear scan inzend_hash_str_findwith sorted lookup helps tiny tables". $PHP_SRC_DIRwith builtsapi/cli/php.- SPEC.md in the task directory (resolved per
_shared/task-dir.md) — created on the first run, read on subsequent runs.
What it produces
SPEC.md(type: idea) in the task directory resolved per_shared/task-dir.md(default$PHP_SRC_DIR/.claude/php-core-dev/idea-<slug>/SPEC.md). Tracks the hypothesis end to end.- Prototype C-code changes under
$PHP_SRC_DIR— explicitly throwaway, not production-ready. - Benchmark scripts and/or
.phptexamples demonstrating the idea. - A
pursue-as-rfc/reframe/killverdict in the final phase.
Phases owned
| # | Phase | Post-guardrail |
|---|---|---|
| 1 | Context | Hypothesis restated in own words; subsystem identified |
| 2 | Hypothesis & Metric | Success metric is concrete and falsifiable |
| 3 | Research | At least one prior-art source ran (owned by /research, hard-gated for idea flow) |
| 4 | Survey & Plan | Smallest viable prototype change identified |
| 5 | Prototype | make -j$(nproc) exits 0 with the patch applied; build is clean |
| 6 | Measurement & Verdict | Numbers (or examples) recorded; honest verdict written |
This skill owns all six phases except Research, which is owned by /research. On each invocation /idea-prototype picks up the first non-done phase and advances it; when the next phase is Research it refuses and instructs the user to run /research (or to mark the phase skipped in SPEC.md with a reason). Research is hard-gated for the idea flow — Survey & Plan will not start until Research is done or skipped. This differs from the bug flow, which soft-warns and proceeds.
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 · 303 lines · 129 tokens per session scan A cde8b2627aa7
idea-prototype is a skill published in the GitHub repository pronskiy/php-src-developer (8 stars, last pushed 4mo ago), licensed MIT. It adds 129 tokens to every session and 5,047 once invoked, about $0.0005 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
integration-fixture
Add a .test integration fixture for one behavior.
behat-skill
Generates Behat BDD tests for PHP with Gherkin feature files and MinkContext for browser testing. Use when user mentions "Behat", "PHP BDD", "Mink", "behat.yml". Triggers on: "Behat", "PHP BDD", "Mink", "behat.yml", "FeatureContext PHP".
Behat BDD Testing
PHP BDD testing with Behat framework using Gherkin feature files, Mink browser extension, context classes, and Symfony integration for behavior-driven acceptance testing.
Codeception Testing
Expert-level Codeception testing skill for PHP applications. Covers acceptance, functional, and unit testing with the Actor pattern, BDD-style syntax, Page Objects, API testing, and database helpers.
Laravel Dusk Testing
Expert-level Laravel Dusk browser testing skill for PHP/Laravel applications. Covers Chrome-based E2E testing, browser assertions, Page Objects, component testing, authentication helpers, and database integration.
phel-lang
Building applications WITH Phel (Lisp that compiles to PHP). Triggers on .phel files, phel-config.php, phel CLI commands (init, run, repl, test, build), or requests to build a Phel app. Skip when working on the Phel compiler itself.