PHP patch coordination · agent skill

One patch ticket.
Every pool accounted for.

Turn the PHP evidence you already have into a per-target ledger—and a clear list of answers still missing.

For agencies and operators coordinating multiple client sites, hosting providers, pools or replicas. No server discovery, automatic patching or security certification.

See the first-run workflow ↓
You bring

An explicit inventory and dated evidence

Declared targets, the running build, incident status, patch and worker-replacement times, and redacted evidence references. Missing information stays missing.

You get

A ledger and the next questions

The helper emits JSON for each target. Your agent can use it to prepare a follow-up table and provider request for your review. Nothing is sent automatically.

Synthetic example · not a host audit

One pool has evidence. The other still needs it.

shop-pool-a PATCH_EVIDENCE_RECORDED

Supplied build and worker evidence meet the incident-specific checks. This records evidence; it does not independently verify the host.

shop-pool-b NEEDS_EVIDENCE

Ask for dated serving-runtime evidence and patch/worker-replacement records tied to this pool. Another pool’s answer does not clear this one.

Expected exit code: 1, because unresolved work remains. The sealed helper produced this local synthetic example; The Agensi-delivered helper reproduced this synthetic result in Claude on October 22, 2026.

Your first run

01

Declare the scope

List every pool or replica you want covered. Use opaque evidence IDs, not passwords, customer records or signed links.

02

Check the execution route

Ask the connected agent to retrieve the complete input contract, licence and helper. If any file or Python is unavailable, stop—do not recreate missing code.

03

Review, then follow up

Run against the explicit assessment date. Review unresolved rows and the draft provider questions. You decide what to send and what to change.

A first-run request to adapt
Use PHP Fleet Patch Ledger with my authorized target inventory and redacted JSON evidence. Read the full input contract first. Retrieve and run the complete helper in memory with Python 3.10+; do not save Agensi skill source. Use my stated assessment date. Return the JSON ledger and a concise owner/action table. Do not scan hosts, patch servers, contact providers or treat an evidence record as security clearance. If retrieval or execution is unavailable, stop and name the missing capability.
Exit codes and unresolved results

0: evidence recorded for all declared targets. 1: unresolved work remains. 2: invalid input, not a usable closure result. None means secure or uncompromised.

If the first run stops

The agent cannot retrieve a supporting file

Stop with EXECUTION_BLOCKED. Confirm the complete package is accessible through the connected Agensi account. Do not reconstruct the script from its description or substitute an old copy.

Python or in-memory execution is unavailable

Use a host that supports Python 3.10+ and the documented delivery route. SKILL.md support alone is insufficient. Do not bypass the Agensi source-saving restriction.

The input is rejected or evidence remains incomplete

Review the input contract for duplicate keys, unknown fields and timestamp formats. Keep unknown values unknown. Request missing provider evidence; never invent a build ID or mark a status fixed to force a pass.

The provider uses a backported vendor package

Review the exact vendor advisory, OS release and package revision. An older upstream-looking version alone cannot settle whether a vendor fix applies. The helper checks supplied evidence structure, not document authenticity.

Access and boundaries

Agensi supplies agent-connected access under its personal, non-transferable licence. Do not save, export or share skill source. Original generated reports may be used for your own or authorized client work, without reproducing package content.

No downloadable-store offer is included in this release. This is evidence organization, not compromise assessment or an assurance that your inventory is complete.

Check your agent setup

Review tested hosts, versions and workflow limits. Evidence for another skill does not establish this product’s compatibility; keep the requirements and limitations above in view.