Agent skill

Cms Detection

by uphiago in uphiago/recon-skills

Identify CMS, frameworks, and server technology stacks on live hosts.

MITAuto-check passedBackend & APIs

Install Cms Detection

skills CLI
$ npx skills add uphiago/recon-skills --skill cms-detection -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install uphiago/recon-skills cms-detection --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/uphiago/recon-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/recon/cms-detection .claude/skills/cms-detection && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cms-detection
GitHub stars
1.3k
Token cost
~2k tokens
SKILL.md length
344 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Identify CMS, frameworks, and server technology stacks on live hosts.

  • Works in 5 steps: Bulk Technology Fingerprinting → CMS-Specific Version Detection → Server and Framework Detection → …
  • Tasks that involve Backend development
  • SKILL.md covers When to Use, Prerequisites, Quick Detection and Procedure, plus 3 more sections
  • Calls curl, jq and shopify; reaches wordpress.org and wpscan.com

What it does

Cms Detection is an agent skill from uphiago/recon-skills. Identify CMS, frameworks, and server technology stacks on live hosts.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires curl, httpx, nuclei

It sits in Backend & APIs, covering Backend development. It works with WordPress, Laravel and Spring Boot. The repository describes itself as: Recon & pentest skill pack. CORS, XSS, SQLi, SSRF, RCE, WordPress, MCP, cloud, subdomain takeover, and more. Field-tested. MIT. Full write-up at hiago.sh. The licence is MIT.

When your agent uses it

  • Tasks that involve Backend development

Example prompts

  • “/cms-detection”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Requires curl, httpx, nuclei

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Bulk Technology Fingerprinting
  2. CMS-Specific Version Detection
  3. Server and Framework Detection
  4. Technology Stack Categorization
  5. Version → CVE Mapping

What it can do on your machine

Read from SKILL.md and the folder at commit 1260244. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • jq
    • shopify
    • rails

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • wordpress.org
    • wpscan.com
    • drupal.org
    • magento.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires curl, httpx, nuclei

    From compatibility in the SKILL.md frontmatter.

Context cost

Cms Detection loads about 2k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 344 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~21
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from uphiago/recon-skills at commit 1260244, republished under its MIT licence (© uphiago). 344 words, ~1,998 tokens.

Download SKILL.mdSave it as .claude/skills/cms-detection/SKILL.md (or your agent's skills folder).
name
cms-detection
description
Identify CMS, frameworks, and server technology stacks on live hosts.
compatibility
Requires curl, httpx, nuclei
version
1.1.0
revision_date
2026-07-25
license
MIT
platforms
linux
tags
recon, CMS, fingerprinting, technology, WordPress, Drupal, Joomla, Magento
category
recon
related_skills
web-enumeration, wordpress-plugin-hunt, visual-recon, wp-mass-recon

CMS Detection

Identify the content management system, web framework, server software, and technology stack of every live host. Know which stack you're attacking before you attack it — a WordPress site needs different tests than a Laravel API or a Spring Boot microservice. Multi-CMS detection covers WordPress, Drupal, Joomla, Magento, Shopify, Wix, Squarespace, Laravel, Django, Express, Spring Boot, and more.

When to Use

  • You have a list of alive hosts and need to categorize them by technology.
  • WordPress-specific tests produced false positives (the site uses Drupal).
  • Need to identify which CMS version is running to match against known CVEs.
  • A host returns generic 200 on all paths — technology detection tells you what it actually runs.
  • Want to find sites running outdated versions of popular CMS platforms.

Prerequisites

  • terminal with httpx, whatweb, wappalyzer, and curl.
  • A list of alive subdomains from skill_view(name='visual-recon') or skill_view(name='subdomain-enumeration').

Quick Detection

bash
# Fastest: httpx with built-in tech detection
cat alive_subs.txt | httpx -silent -tech-detect -o tech_detect.txt

# Deep: whatweb with aggressive checks
whatweb -i alive_subs.txt -a 3 -t 50 --log-brief=cms_results.txt

Procedure

Phase 1 — Bulk Technology Fingerprinting
bash
# httpx — fast tech detection using Wappalyzer signatures
cat alive_subs.txt | httpx -silent -tech-detect -o tech_httpx.txt

# Parse results: extract unique technologies with counts
cat tech_httpx.txt | awk -F' [' '{print $2}' | tr -d ']' | tr ',' '\n' \
  | sed 's/^ *//' | sort | uniq -c | sort -rn > tech_summary.txt

# whatweb — deeper, identifies specific CMS versions
whatweb -i alive_subs.txt -a 3 -t 50 \
  --log-brief=cms_results.txt \
  --log-json=cms_results.json

# Parse whatweb JSON for versioned findings
cat cms_results.json | jq -r '.[] | select(.version != null) | "\(.target): \(.plugin) \(.version)"' \
  | sort -u > versioned_cms.txt
Phase 2 — CMS-Specific Version Detection
WordPress
bash
# Generator meta tag
curl --max-time 30 --connect-timeout 10 -sk "https://target.com" | grep -Eo '<meta name="generator"[^>]*content="WordPress [^"]+' | head -1

# RSS feed
curl --max-time 30 --connect-timeout 10 -sk "https://target.com/feed/" | grep -Eo '<generator>https://wordpress.org/\?v=[^<]+' | head -1

# readme.html (often left accessible)
curl --max-time 30 --connect-timeout 10 -sk "https://target.com/readme.html" | grep -Eo "Version [0-9.]+" | head -1

# wp-json namespace
curl --max-time 30 --connect-timeout 10 -sk "https://target.com/wp-json/" | jq -r '.namespaces[]' 2>/dev/null
Drupal
bash
# CHANGELOG.txt (Drupal's canonical version leak)
curl --max-time 30 --connect-timeout 10 -sk "https://target.com/CHANGELOG.txt" | head -5

# Drupal specific paths
curl --max-time 30 --connect-timeout 10 -skI "https://target.com/user/login" | grep -i "drupal\|x-generator"
curl --max-time 30 --connect-timeout 10 -skI "https://target.com/node/1"
Joomla
bash
# Joomla version files
curl --max-time 30 --connect-timeout 10 -sk "https://target.com/administrator/manifests/files/joomla.xml" | grep -Eo '<version>[^<]+' | head -1
curl --max-time 30 --connect-timeout 10 -sk "https://target.com/language/en-GB/en-GB.xml" | grep -Eo '<version>[^<]+'

# Meta tag
curl --max-time 30 --connect-timeout 10 -sk "https://target.com" | grep -Eo '<meta name="generator"[^>]*content="Joomla[^"]+' | head -1
Magento
bash
# Magento version file
curl --max-time 30 --connect-timeout 10 -sk "https://target.com/magento_version" | head -1
# Composer lock
curl --max-time 30 --connect-timeout 10 -sk "https://target.com/composer.lock" | jq -r '.packages[] | select(.name=="magento/magento2-base") | .version' 2>/dev/null
Laravel
bash
# Laravel debug info
curl --max-time 30 --connect-timeout 10 -sk "https://target.com" | grep -Eo 'Laravel v[0-9.]+'
# Composer lock
curl --max-time 30 --connect-timeout 10 -sk "https://target.com/composer.lock" | jq -r '.packages[] | select(.name=="laravel/framework") | .version' 2>/dev/null
Phase 3 — Server and Framework Detection
bash
# Server header — often removed but check anyway
for host in $(cat alive_subs.txt); do
  echo -n "$host: "
  curl --max-time 30 --connect-timeout 10 -skI "https://$host" | grep -i "server:\|x-powered-by:" | tr '\n' ' '
  echo
  sleep 0.3
done > server_headers.txt

# Common server signatures and what they mean
# nginx → likely PHP-FPM or Node.js proxy
# Apache → shared hosting, cPanel
# IIS → Windows, ASP.NET
# LiteSpeed → shared hosting, WordPress optimized
# cloudflare → CDN/WAF in front, need origin-ip-discovery
# Microsoft-IIS/10.0 → Windows Server 2016+

# Framework detection via specific paths
# Django admin: /admin/ → redirect to /admin/login/
# Rails: /assets/application-*.js pattern
# Express: X-Powered-By: Express
# Spring Boot: /actuator/health returns {"status":"UP"}
# Next.js: /_next/static/ chunks
Phase 4 — Technology Stack Categorization
bash
# Categorize hosts by CMS for targeted testing
echo "=== WORDPRESS ==="
grep -i "wordpress" tech_detect.txt

echo "=== DRUPAL ==="
grep -i "drupal" tech_detect.txt

echo "=== OTHER CMS ==="
grep -iE "joomla|magento|shopify|wix|squarespace|ghost" tech_detect.txt

echo "=== FRAMEWORKS ==="
grep -iE "laravel|django|rails|express|spring|next\.js|nuxt" tech_detect.txt

echo "=== E-COMMERCE ==="
grep -iE "woocommerce|magento|shopify|prestashop|opencart" tech_detect.txt

echo "=== NO CMS (Static/Custom) ==="
cat alive_subs.txt | httpx -silent -td \
  | grep -v -iE "wordpress|drupal|joomla|magento|laravel|django|rails"
Phase 5 — Version → CVE Mapping
bash
# Map detected versions to known CVEs
# WordPress: check https://wpscan.com/wordpress-security/vulnerability-database/
# Drupal: check https://www.drupal.org/security
# Magento: check https://magento.com/security/patches

# searchsploit — local ExploitDB search
searchsploit wordpress 6.5
searchsploit drupal 10.2
searchsploit joomla 5.1

# nuclei — automated CVE detection on detected CMS
nuclei -l wordpress_sites.txt -t nuclei-templates/http/cves/2024/

Pitfalls

  • Generator meta tags can be spoofed. A site claiming "WordPress 7.0" may be running 6.5. Cross-check with readme.html or RSS feed.
  • Technology detection is signature-based. Custom themes may strip or modify signatures.
  • CDN caching may serve stale version info. Force cache bypass with random query parameters.
  • whatweb can trigger WAF blocks on aggressive scans. Use -a 2 (less aggressive) on protected targets.
  • Headless CMS (Strapi, Contentful) has no version file. Look for API endpoints instead.

Verification

  1. At least two independent methods confirm the same CMS/version (meta tag + readme + wp-json).
  2. Version-specific paths exist (e.g., /wp-admin/ for WordPress, /user/login for Drupal).
  3. Framework-specific endpoints respond correctly (e.g., /actuator/health for Spring Boot).
  4. Document: hostname, CMS, version, detection method, and whether the version has known CVEs.
  • web-enumeration — Once CMS is identified, enumerate its specific paths and endpoints.
  • wordpress-plugin-hunt — Deep plugin version detection for WordPress targets.
  • wp-mass-recon — Batch WordPress vulnerability scanning.
  • visual-recon — Confirm CMS detection with visual screenshot verification.
  • deep-invade — Run nuclei CVE scans against detected versions.

© uphiago, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in recon/cms-detection of uphiago/recon-skills.

Open the folder on GitHubat commit 1260244

Compare with similar skills

Cms Detection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cms Detection compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cms Detection this skilluphiago/recon-skills1.3k—~2kAutomated safety check: PassMIT
Php Framework Auditwgpsec/AboutSecurity1.8k—~767Automated safety check: NotesNone
PayRam Checkout IntegrationPayRam/payram-mcp158—~3.4kAutomated safety check: NotesNone
Payram Webhook IntegrationPayRam/payram-mcp158—~3.6kAutomated safety check: NotesNone
Wordpressericrisco/rsc-harness156—~3kAutomated safety check: PassMIT
Olore Zeptomail Latestolorehq/olore103—~1.3kAutomated safety check: PassMIT

Similar skills

  • Php Framework Audit

    wgpsec/AboutSecurity

    PHP 框架特定安全审计。当在 PHP 白盒审计中已识别目标使用特定框架、 需要检查框架特有安全机制和常见配置缺陷时触发。

    1.8k GitHub stars~767 tokensUpdated 3 days ago
    Backend & APIsAuto-check: notes
  • Adds crypto checkout to a web app with PayRam: create a payment from your backend, send the customer to the payment page, then confirm the result.

    158 GitHub stars~3.4k tokensUpdated 1 mo ago
    Backend & APIsAuto-check: notes
  • Integrate PayRam webhook handlers for real-time payment and payout event notifications.

    158 GitHub stars~3.6k tokensUpdated 1 mo ago
    Backend & APIsAuto-check: notes
  • Wordpress

    ericrisco/rsc-harness

    A skill your agent uses when building or hardening WordPress sites or WooCommerce stores and treating WordPress as the product rather than just writing PHP — block themes with theme.json, plugins…

    156 GitHub stars~3k tokensUpdated today
    Backend & APIsAuto-check passed
  • Local Zoho ZeptoMail documentation reference (latest). An agent skill from olorehq/olore.

    103 GitHub stars~1.3k tokensUpdated today
    Backend & APIsAuto-check passed
  • Audit PHP web application source for critical vulnerabilities using PHP's specific sink and footgun catalog — object injection via unserialize and phar:// POP chains, type-juggling and magic-hash…

    156 GitHub stars~2.8k tokensUpdated 1 mo ago
    SecurityAuto-check passed

More from uphiago/recon-skills

All 23 skills in this repo
  • Flags API endpoints whose data or actions look like they should need a login but currently don't, as part of authorized security testing.

    1.3k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed
  • Error Log Mining

    uphiago/recon-skills

    Mine errorlog for creds, paths, SQL when leak hunt finds. An agent skill from uphiago/recon-skills.

    1.3k GitHub stars~3.3k tokensUpdated 1 mo ago
    Auto-check passed
  • JS Secrets Extraction

    uphiago/recon-skills

    Analyze JS bundles and source maps for hardcoded secrets, API keys, JWTs, and internal endpoints

    1.3k GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Recon Playbook

    uphiago/recon-skills

    A skill your agent uses when starting or restructuring an authorized external web and API assessment.

    1.3k GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Web Enumeration

    uphiago/recon-skills

    Sensitive file scanning, path traversal bypass, vHost enum, .env extract, log mining, Varnish detect

    1.3k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check: notes
  • 401 403 Bypass Techniques

    uphiago/recon-skills

    A skill your agent uses when protected HTTP routes return 401 or 403.

    1.3k GitHub stars~3.1k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Cms Detection

What does Cms Detection do?

Identify CMS, frameworks, and server technology stacks on live hosts. Cms Detection is an agent skill from uphiago/recon-skills. Identify CMS, frameworks, and server technology stacks on live hosts.

When should I use Cms Detection?

Cms Detection fits situations like: tasks that involve Backend development.

How do I install Cms Detection in Claude Code?

Run `npx skills add uphiago/recon-skills --skill cms-detection -a claude-code`. Or copy the skill folder (recon/cms-detection in uphiago/recon-skills) into .claude/skills/cms-detection in your project. Claude Code loads it when a task matches its description.

How do I install Cms Detection in Codex?

Run `npx skills add uphiago/recon-skills --skill cms-detection -a codex`. Or copy the skill folder (recon/cms-detection in uphiago/recon-skills) into .agents/skills/cms-detection in your project. Codex loads it when a task matches its description.

Can I use Cms Detection in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add uphiago/recon-skills --skill cms-detection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cms-detection, .gemini/skills/cms-detection, .github/skills/cms-detection and .opencode/skills/cms-detection in your project.

What does Cms Detection need to run?

Going by SKILL.md and its folder, Cms Detection needs the command-line tools its instructions call (curl, jq, shopify and rails). Our summary lists: Node.js. Compatibility (from SKILL.md): Requires curl, httpx, nuclei.

Does Cms Detection access the network?

SKILL.md names 4 domains. In commands or code: wordpress.org, wpscan.com, drupal.org and magento.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Cms Detection safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cms Detection use?

Cms Detection is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cms Detection use?

About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cms Detection?

Skills that share tags, products or a category with Cms Detection: Php Framework Audit (wgpsec/AboutSecurity, 1.8k stars), PayRam Checkout Integration (PayRam/payram-mcp, 158 stars), Payram Webhook Integration (PayRam/payram-mcp, 158 stars) and Wordpress (ericrisco/rsc-harness, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cms Detection?

uphiago (a GitHub user) maintains it in uphiago/recon-skills, which has 1,294 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on September 1, 2026.

Source: uphiago/recon-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.