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 skills/anhnguyen0905/codex-mcp/exec-phpnpx skills add anhnguyen0905/codex-mcp --skill exec-phpgit clone --depth 1 https://github.com/anhnguyen0905/codex-mcpWhat 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.00036 | $0.00335 |
| Opus 5 | $0.00018 | $0.00168 |
| Sonnet 5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
exec-php 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 2d 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.
What it actually says
PHP Idioms (embed when project is PHP)
PHP standards:
- declare(strict_types=1) at the top of every file; type every param, return, and property; use
enums and readonly properties where the version supports them.
- Errors: throw specific exceptions (extend the framework's or SPL types); catch narrowly; never
suppress with @; use finally for cleanup; never return false/null to signal errors that callers
will forget to check.
- Immutability: readonly properties / value objects for data that shouldn't change after construction;
avoid mutating arrays passed by reference unless the API contract says so.
- Follow PSR-12 formatting and PSR-4 autoloading; match Composer package/namespace structure. Add
dependencies only via composer.json.
- Framework (if Laravel/Symfony): use its idioms — Eloquent/Doctrine correctly (no N+1: eager-load
relations), form requests / validators for input, dependency injection over facades in new code,
migrations for schema. Don't hand-roll what the framework provides.
- Security: parameterized queries / query builder only (never interpolate input into SQL); escape
output in templates; validate and sanitize all request input at the boundary.
- Tests: PHPUnit (or Pest if the repo uses it); arrange-act-assert; data providers for case tables;
assert behavior, match existing test namespace/layout.
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.
- 2d ago First seen · 27 lines · 36 tokens per session scan A 35d5b94743b5
exec-php is a skill published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed 11d ago), licensed MIT. It adds 36 tokens to every session and 335 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 skills, from other repositories
laravel-actions
Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions. Use when implementing reusable action classes (object/controller/job/listener/command), converting service classes/controllers/jobs into actions, orchestrating workflows via faked actions, or debugging action entrypoints and wiring.
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
laravel-best-practices
Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization…
routes
Generate route configuration for CatchAdmin module.
create-powergrid-plugin
Create a complete PowerGrid plugin from scratch, including PHP class, Column macro, Blade view, Alpine.js component, and registration.
create-module
Scaffold a new Marko module — a self-contained Composer package with composer.json, namespaced src/, and Pest tests. Use this skill whenever the user asks to create, add, or scaffold a new Marko module or package. Concrete triggers: 'create a module named payment', 'scaffold an acme/blog package', 'add a new module…