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 dayfinggg/openai-codex-agent-skills --skill php-composer-changegit clone --depth 1 https://github.com/dayfinggg/openai-codex-agent-skillsWrote 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/dayfinggg/openai-codex-agent-skills/php-composer-change)<a href="https://agentmods.dev/skills/dayfinggg/openai-codex-agent-skills/php-composer-change"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/php-composer-change/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/dayfinggg/openai-codex-agent-skills/php-composer-change"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/php-composer-change.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.00039 | $0.00373 |
| Opus 5.5 | $0.00016 | $0.00149 |
| Sonnet 5.5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
php-composer-change 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 today.
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
Keep PHP dependency changes reproducible and limited to the requested graph.
- Read composer.json, composer.lock, platform configuration, repositories, allowed plugins, and scripts. Identify the actual PHP executable, extensions, and project Composer command. Never print authentication files or tokens.
- Distinguish environment restoration from dependency updates. With a valid lockfile, installation must use its resolved versions. An installation failure does not authorize an update.
- For an authorized update, choose the smallest package set and compatible constraints. Use a resolution dry run when useful. Read the migration documentation for changed major versions.
- Inspect what scripts and plugins execute before running them. Reuse the project's authorized tooling. Do not permanently disable required behavior to hide a failure or run an unreviewed network installer.
- Update the manifest and lockfile through the selected dependency manager. Do not hand-edit lockfile versions or integrity hashes.
- Review direct and transitive changes, extension requirements, autoloading, and conflicts. Check the deployment platform as well as local PHP and config.platform.
- Run appropriate validate, check-platform-reqs, advisory checks, and application tests. An unavailable advisory service is an unverified result, not evidence of no vulnerabilities.
Do not use --ignore-platform-reqs as a permanent compatibility fix. Change package stability, download sources, or plugin permissions only when the task requires it.
Finish with a consistent lockfile and verified platform compatibility. Check command semantics in the Composer CLI and Composer scripts.
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.
- today First seen · 20 lines · 39 tokens per session scan A 1756d820afbc
php-composer-change is a skill published in the GitHub repository dayfinggg/openai-codex-agent-skills (8 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 373 once invoked, about $0.0002 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-10-30.
Other skills, from other repositories
kirby-ide-support
Improves IDE autocomplete and static analysis in Kirby projects with PHPDoc hints and Kirby IDE helper generation. Use when types are missing or IDE support is degraded.
spatie-guidelines
Spatie's PHP, Laravel, JavaScript and Vue coding guidelines and conventions. Use when writing or reviewing PHP, Laravel, JavaScript, or Vue code for Spatie projects or packages. Covers code style, type declarations, docblocks, control flow, naming, routing, controllers, Blade, validation, comments, testing (Pest)…
spatie-package-skeleton
Guide for creating PHP and Laravel packages using Spatie's package-skeleton-laravel and package-skeleton-php templates. Use when the user wants to create a new PHP or Laravel package, scaffold a package. Also use when building customizable packages — covers proven patterns for extensibility (events, configurable…
speeding-up-laravel-tests
Use when Laravel/Pest test suites are slow, CI duration is growing, individual tests take seconds, or the user asks to speed up, optimize, or profile tests. Covers factories, fakes, config caching, XDebug/pcov, BCRYPTROUNDS, LazilyRefreshDatabase, and stray HTTP requests.
livewire-4
Build Livewire 4 components and applications. Use when creating reactive Laravel interfaces, single-file components, multi-file components, page components, forms, actions, or any Livewire-based UI. Triggers include "Livewire component", "wire:model", "wire:click", building interactive Laravel UIs, or working with…
laravel-auth
Use when implementing user authentication, API tokens, social login, or authorization in Laravel 13.