agentleFS
Sign inStart free
mastereadmasteread/php2shell-checker-claude/skills/url/SKILL.md

url

Skill2 starsChanged 25 days agoApache-2.0View on GitHub

Check the PHP version a website advertises in its HTTP headers and report whether it is patched against PHP2Shell (October 2026 PHP security releases). Use when the user gives a URL or hostname and asks if it is vulnerable, patched or up to date.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. stepanbeseda/RohlikCookidoo★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If Node is older than 22.23.4 on 22.x, 24.22.1 on 24.x or 26.12.1 on 26.x, or on an end-of-life line, tell the user to update Node and ask …

    line 17
  2. Distinctive:

    If no target was given, ask the user for one.

    line 29
  3. Very specific:

    Run the command exactly as shown, as a single command.

    line 37
  4. Very specific:

    If the checker prints a Node.js warning on stderr, pass it on to the user.

    line 41
  5. Distinctive:

    Do not run exploit probes or send any other requests to the target.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PHP2Shell refers to CVE-2026-109618 and CVE-2026-109619, the two critical remote code execution vulnerabilities fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 on October 21, 2026 (https://www.php.net/archive/2026.php#2026-10-21-5). PHP 8.1 and older received no upstream release.

First run node --version. The checker connects to servers you do not control, and the Node.js October 21, 2026 security releases fixed a Brotli decoder remote code execution and TLS hostname bypasses (https://nodejs.org/en/blog/vulnerability/october-2026-security-releases). If Node is older than 22.23.4 on 22.x, 24.22.1 on 24.x or 26.12.1 on 26.x, or on an end-of-life line, tell the user to update Node and ask before continuing.

Then run the bundled checker against the target. Use HTTPS for a bare hostname:

node ${CLAUDE_SKILL_DIR}/scripts/phpcheck.js "https://example.com" --json

Target: $ARGUMENTS

If no target was given, ask the user for one. Check only sites the user owns or is authorized to assess.

The checker sends one HEAD request (or a GET if HEAD returns 405 or 501) and reads the Server and X-Powered-By headers. It does not follow redirects. If the site redirects, such as from http:// to https:// or to www., offer to check the final URL.

Run the command exactly as shown, as a single command. Do not chain echo, pipes or other commands onto it: the JSON output already includes exit_code, and a modified command is no longer pre-approved.

If the checker prints a Node.js warning on stderr, pass it on to the user.

Exit codes 1 and 3 mean vulnerable and unknown. They are results, not execution failures. Exit code 2 means invalid arguments.

Report the PHP version, the patch status, and the update needed:

  • vulnerable: the version is at or below the cutoff for its branch. Recommend updating to a newer patch release of that branch or a supported branch.
  • ok: the version is newer than the cutoff. Headers can be changed, so a server-side check (/phpcheck:server) is stronger evidence.
  • unknown: the version is hidden, the branch is not listed, or it is a prerelease. unknown does not mean patched. Suggest /phpcheck:server if the user has server access.

Vendor backports (Debian, Ubuntu, RHEL and others) may fix an older upstream version, so a vulnerable result on a distribution build should be confirmed against that vendor's advisory.

Do not run exploit probes or send any other requests to the target.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free