What is update-php-images?

A command for updating dependencies and development tools in three Specsnl PHP Dockerfile variants: FPM, Apache, and FrankenPHP.

Use it to safely prepare coordinated dependency updates on the main branch, using a clean working tree and isolated commits.

It prevents shared versions from being updated in only one Dockerfile and stops when repository or update checks fail.

update-php-images — Command for Claude Code by specsnl/agent-specs

Install

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.

Clone the repo

git clone --depth 1 https://github.com/specsnl/agent-specs

Made for: Claude Code.

Or install docker, the plugin that ships this one along with the rest of its 1 skill, 2 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/specsnl/agent-specs/update-php-images/github.svg)](https://agentmods.dev/commands/specsnl/agent-specs/update-php-images)

Your own site

<a href="https://agentmods.dev/commands/specsnl/agent-specs/update-php-images"><img src="https://agentmods.dev/badge/commands/specsnl/agent-specs/update-php-images/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/specsnl/agent-specs/update-php-images"><img src="https://agentmods.dev/badge/commands/specsnl/agent-specs/update-php-images.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,351 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00022	$0.02351
Opus 5.5	$0.00009	$0.00940
Sonnet 5.5	$0.00004	$0.00470
Haiku 4.5	$0.00002	$0.00235

Measured 1mo ago against content hash af1ca09eeb4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

plugins/docker/commands/update-php-images.md · 213 lines

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 to main first.
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 from origin/main.
  - If behind main and has NO unique commits → reset updates to origin/main.
  - If it contains unique commits → abort and notify user.
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-trixie
apache/Dockerfile: FROM php:<version>-apache-trixie
frankenphp/Dockerfile: FROM dunglas/frankenphp:<frankenphp-version>-php<php-version>-trixie

Check Docker Hub for the latest php:8.5.x-fpm-trixie tag. Only consider patch updates within the 8.5.x series — do not update to a different minor or major PHP version.
Check Docker Hub for the latest dunglas/frankenphp tag that matches the pattern x.x.x-php8.5.x-trixie. Only consider updates that keep the PHP 8.5.x series.
Update the FROM lines 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.

Read the full file on GitHub · 213 lines

Changes

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.

1mo ago Changed af1ca09eeb4d
1mo ago First seen · 213 lines · 22 tokens per session scan A 77b49754d398

Subscribe to this mod's changes

update-php-images is a command published in the GitHub repository specsnl/agent-specs (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 2,351 once invoked, about $0.0001 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-08-31.

Containers DevOps and cloud

create-docker-mcp-tunnel

Stand up an Anthropic MCP tunnel locally with Docker Compose so Claude can call a private MCP server (manual-credentials quickstart).

anthropics/claude-plugins-official · 26 tokens

cisco-isovalent-platform-setup

Install and operate Cilium networking and Tetragon runtime security on Kubernetes in OSS or Enterprise edition, with Hubble and Enterprise add-on paths. The coverage catalog explicitly maps newer Isovalent Enterprise Platform areas, including VM networking and Isovalent Load Balancer, to their supported, gated, or…

chambear2809/splunk-cisco-skills · 0 tokens

update-php-images

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Goal

Phase 1 --- Repository Safety Checks

Phase 2 --- PHP Base Image Updates

What this file has done since we first saw it

Other commands, from other repositories

create-docker-mcp-tunnel

cisco-isovalent-platform-setup

build-agent

application-crud

review-helm

create-operator