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 commands/specsnl/agent-specs/update-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.00022 | $0.02349 |
| Opus 5 | $0.00011 | $0.01175 |
| Sonnet 5 | $0.00004 | $0.00470 |
| Haiku 4.5 | $0.00002 | $0.00235 |
Grade A, and why
update-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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
Perform a full dependency update across all three Dockerfile variants (fpm, apache, frankenphp) in a safe, reproducible way.
Critical rule: Any version that appears in more than one Dockerfile must be updated across all affected Dockerfiles in a single commit. Never update a shared version in only one Dockerfile.
If any step fails, STOP immediately and report the error.
Phase 1 --- Repository Safety Checks
- Verify the current branch is
main. If not, abort and instruct the user to switch tomainfirst. - Ensure the working (git) tree is clean:
- No staged changes
- No unstaged changes
- No untracked files
- If not clean: Abort immediately — inform the user to commit or stash changes.
- Synchronize with remote:
git fetch --prune - Prepare branch
updates:- If branch does not exist → create from
origin/main - If branch exists:
- If fully merged into
main→ delete locally and recreate fromorigin/main. - If behind
mainand has NO unique commits → resetupdatestoorigin/main. - If it contains unique commits → abort and notify user.
- If fully merged into
- If branch does not exist → create from
- Check if the branch does not already exist on the remote. If it does, abort and inform the user to delete the remote branch first.
Always branch from latest origin/main.
Phase 2 --- PHP Base Image Updates
The three Dockerfiles use different base images but all track the same PHP 8.5.x patch series:
fpm/Dockerfile:FROM php:<version>-fpm-trixieapache/Dockerfile:FROM php:<version>-apache-trixiefrankenphp/Dockerfile:FROM dunglas/frankenphp:<frankenphp-version>-php<php-version>-trixie
- Check Docker Hub for the latest
php:8.5.x-fpm-trixietag. Only consider patch updates within the8.5.xseries — do not update to a different minor or major PHP version. - Check Docker Hub for the latest
dunglas/frankenphptag that matches the patternx.x.x-php8.5.x-trixie. Only consider updates that keep the PHP 8.5.x series. - Update the
FROMlines in all three Dockerfiles if newer versions are available. - Check
git status. Commit all three Dockerfiles together in a single commit if there are any changes. Commit message:chore(deps): Update PHP base image versions. - If there are no changes, skip the commit and move on.
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 · 213 lines · 22 tokens per session scan A 77b49754d398
update-php-images is a command published in the GitHub repository specsnl/agent-specs (2 stars, last pushed 16d ago), licensed MIT. It adds 22 tokens to every session and 2,349 once invoked, about $0.0001 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 commands, from other repositories
sandbox
Manage sandbox backends and tooling.
dockerfile
Validate Dockerfiles for GPU/CUDA configuration issues before building.
index
Command "index" from thrashr888/agentkernel, covering commands, quick reference, daily drivers (root level), sandbox lifecycle (sandbox / sb) and ssh (ssh).
deploy
Build, test, deploy with staged rollout.
cisco-isovalent-platform-setup
Install the Isovalent platform on Kubernetes (Cilium CNI, Hubble observability, Tetragon eBPF runtime security) in either OSS or Enterprise edition. Renders Helm values and install/upgrade scripts; this is the platform install prerequisite for the Splunk Observability + Splunk Platform integration done by…
deploy
Build a container image, push it, and deploy the service to the Akka platform. This is the transition from local development to development on the AAO platform.