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/specsnl/agent-specs/php-imagesnpx skills add specsnl/agent-specs --skill php-imagesgit clone --depth 1 https://github.com/specsnl/agent-specsWhat 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.00050 | $0.01387 |
| Opus 5 | $0.00025 | $0.00694 |
| Sonnet 5 | $0.00010 | $0.00277 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
php-images 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP Images Skill
This skill provides information about the PHP images used in the Specsnl projects, including where to find the source files and how to locate sibling images for other PHP versions.
What are the PHP images?
The PHP images are Docker images that serve as the base for the various PHP environments used in Specsnl projects. These images are built on top of official PHP images and include additional dependencies and configurations specific to our needs.
Each PHP image repository follows a consistent structure with three main Dockerfiles (variants):
fpm/Dockerfile: The Dockerfile for the FPM variant of the image.apache/Dockerfile: The Dockerfile for the Apache variant of the image.frankenphp/Dockerfile: The Dockerfile for the FrankenPHP variant of the image.
Furthermore, there is a files directory that contains additional files used during the build process, such as
configuration files and scripts.
files/general: Contains files that are shared across all PHP Dockerfiles.files/<variant_name>: Contains files specific to the<variant_name>variant of the image.
Supported PHP versions
Specsnl maintains images for 3 supported PHP versions at any given time. To determine the current supported versions,
fetch the endoflife.date API: https://endoflife.date/api/v1/products/php/. This returns a JSON array of PHP releases
with their active-support and security-support end dates. Use the 3 most recent versions that have not yet reached
end-of-life as the supported set.
If a Specsnl repository for the newest PHP version does not exist yet, we are still supporting the previous version as
the latest one. For example, if PHP 8.5 is the newest version but the php85 repository has not been created yet, we
are still treating PHP 8.4 as the latest.
Where can I find the source files on GitHub?
The source files for the PHP images can be found in the repositories that follow the following structure:
https://github.com/specsnl/php<major><minor>. For example, for PHP 8.5, the source files are located in
https://github.com/specsnl/php85.
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 · 109 lines · 50 tokens per session scan A c74beedb5105
php-images is a skill published in the GitHub repository specsnl/agent-specs (2 stars, last pushed 17d ago), licensed MIT. It adds 50 tokens to every session and 1,387 once invoked, about $0.0003 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
reproduce-issue
The single skill for reproducing an nx issue. Given a GitHub issue number (human entry) OR explicit repro parameters (agent entry), it runs the reproduction ENTIRELY inside an isolated Docker sandbox — gVisor on Linux, the Docker VM on macOS — so the untrusted repro's install scripts and commands never execute on the…
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
atmos-aws-ecr
AWS ECR commands in Atmos: atmos aws ecr login, ECR auth integrations, Docker credential writes, registry login via identity or explicit registry.
windows-builder
Build Windows images with Packer using WinRM communicator and PowerShell provisioners. Use when creating Windows AMIs, Azure images, or VMware templates.
release-openclaw-plugin-testing
Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E, Package Acceptance, and Testbox proof.