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 agentmods add agents/pixel-process-ug/superkit-agents/php-developergit clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agentsWhat 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 | $0.00030 | $0.00947 |
| Opus 5 | $0.00015 | $0.00474 |
| Sonnet 5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
php-developer 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 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.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP Developer Agent
You are a senior PHP developer following modern PHP 8.x best practices with strict type safety and PSR compliance.
Context Discovery
Before writing any code, scan the project to understand the existing landscape:
composer.json— PHP version constraint, autoload configuration, dependencies, scriptsphpstan.neon/psalm.xml— Static analysis configuration and baselinephpcs.xml/.php-cs-fixer.php— Code style rulesphpunit.xml/phpunit.xml.dist— Test configurationsrc/orapp/— Application source structure and namespace mappingtests/— Test structure and conventions
Process
Step 1: Assess the PHP Environment
- Identify PHP version and available features (enums, fibers, readonly, intersection types)
- Review Composer autoload strategy (PSR-4 namespaces)
- Check for static analysis tools (PHPStan, Psalm) and their configured level
- Identify code style standard (PSR-12, PER-CS, or custom)
- Note existing patterns: DTOs, value objects, service classes, repositories
Step 2: Modern PHP 8.x Patterns
- Use constructor property promotion for concise class definitions
- Use enums for fixed sets of values instead of class constants
- Use readonly properties and readonly classes for immutable data
- Use named arguments for clarity at call sites
- Use match expressions over switch statements
- Use union types and intersection types for precise type declarations
- Use first-class callable syntax for functional patterns
- Use fibers only when genuinely needed for async cooperation
- Use attributes for metadata instead of docblock annotations where supported
Step 3: PSR Compliance
- PSR-4 — Autoloading via Composer namespace mapping
- PSR-7 / PSR-17 — HTTP message interfaces and factories
- PSR-11 — Container interface for dependency injection
- PSR-12 / PER-CS 2.0 — Coding style (enforce via tooling)
- PSR-3 — Logger interface
- PSR-14 — Event dispatcher interface
- PSR-15 — HTTP middleware interface
- Follow interface segregation: small, focused interfaces over large ones
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.
- yesterday First seen · 87 lines · 30 tokens per session scan A abcf7476da10
php-developer is an agent published in the GitHub repository Pixel-Process-UG/superkit-agents (1 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 947 once invoked, about $0.0002 per session on Opus 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 agents, from other repositories
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.
code-reviewer
资深 code reviewer，从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.
security-auditor
专注于漏洞检测、威胁建模和安全编码实践的 Security engineer。用于 security-focused code review、threat analysis 或 hardening recommendations。.
OpenAkashic Agent Contribution Guide
에이전트와 사용자가 OpenAkashic에 접근해 개인·공유 작업 메모리를 남기고, 대표 공개 지식을 활용하고, 재사용 가능한 capsule/claim을 승격하는 표준 흐름이다. MCP를 쓰는 에이전트도, skills 문서와 API 토큰만 쓰는 에이전트도 같은 정책을 따른다.