deployment-inspection

deployment-inspection is a skill for Claude Code, Codex from S3YED/appie-kit. It costs 35 tokens per session (2,008 once invoked), scanned A, original, MIT.

A workflow for investigating a live website, from identifying its hosting platform to finding subdomains, deployment details, JavaScript bundles, and source repositories.

In plain words
What is it for?
Inspecting client deployments, detecting platforms such as Netlify or Vercel, discovering subdomains, examining deployed code, and locating related repositories.
Why use it?
It turns a deployed site into a set of technical clues when the underlying project or hosting setup is unknown.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Inspecting client deployments, detecting platforms such as Netlify or Vercel, discovering subdomains, examining deployed code, and locating related repositories.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/s3yed/appie-kit/deployment-inspection
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.

Any agent
npx skills add S3YED/appie-kit --skill deployment-inspection
Clone the repo
git clone --depth 1 https://github.com/S3YED/appie-kit

Made for: Claude Code, Codex.

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.

agentmods badge for deployment-inspection

README.md
[![agentmods](https://agentmods.dev/badge/skills/s3yed/appie-kit/deployment-inspection/github.svg)](https://agentmods.dev/skills/s3yed/appie-kit/deployment-inspection)
Your own site
<a href="https://agentmods.dev/skills/s3yed/appie-kit/deployment-inspection"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/deployment-inspection/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.

agentmods 80×15 button for deployment-inspection

Your own site · 80×15
<a href="https://agentmods.dev/skills/s3yed/appie-kit/deployment-inspection"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/deployment-inspection.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,008 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.02008
Opus 5 $0.00017 $0.01004
Sonnet 5 $0.00007 $0.00402
Haiku 4.5 $0.00003 $0.00201

Measured 7d ago against content hash fde6ce714fa5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

deployment-inspection scanned grade A with 1 finding 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 7d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sI https://domain.com | grep -i "server\|x-powered-by\|x-served-by\|cache-status"
skills/devops/deployment-inspection/SKILL.md · 194 lines

How it starts

The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deployment Inspection

When to Use

Load this skill when the user says:

  • "Vind het project [domain]" / "Open de site"
  • "Check de deploy" / "Kijk in de codebase"
  • "Waar staat dit project?"
  • Any request to investigate a live web project, its hosting platform, codebase, or deployment setup

Detection Flow

1. Platform Detection

Run these checks in order to identify where the site is hosted:

# Check HTTP response headers
curl -sI https://domain.com | grep -i "server\|x-powered-by\|x-served-by\|cache-status"
Header value Platform
server: cloudflare Behind Cloudflare — check further
server: Netlify + Netlify Edge cache Netlify
server: Vercel Vercel
x-powered-by: Express Custom Node.js server
x-served-by: Webflow or scripts from cdn.prod.website-files.com Webflow

Webflow confirmation — check script sources in the HTML for cdn.prod.website-files.com:

curl -s https://domain.com | grep -o 'src="[^"]*"' | grep -i 'website-files'

2. Subdomain Discovery

When the user says the app is at a subdomain that doesn't resolve:

# Check DNS first
dig booking.domain.com +short
dig book.domain.com +short
dig app.domain.com +short

# Check nameservers for hosting clues
dig domain.com NS +short

# Check local screenshot tool configs for the real URL
grep -r 'domain.com\|domain' ~/clawd/projects/*/screenshot-tool.js 2>/dev/null
grep -r 'domain.com\|domain' ~/clawd/tools/*.js 2>/dev/null

Known pattern: The screenshot-tool.js in Weblyfe projects often has the correct subdomain URLs for client sites. Always check there first when a subdomain doesn't resolve.

3. Netlify API Access

When the site is confirmed on Netlify:

# Token location
source ~/.weblyfe-secrets/.env  # exports NETLIFY_AUTH_TOKEN

# List sites and search by name
curl -s -H "Authorization: Bearer $NETLIFY_AUTH_TOKEN" \
  "https://api.netlify.com/api/v1/sites?page=1&per_page=100" | \
  python3 -c "import sys,json; sites=json.load(sys.stdin); [print(f\"{s.get('name')} | {s.get('custom_domain','-')} | {s.get('ssl_url','-')}\") for s in sites]"

# Get full site info
curl -s -H "Authorization: Bearer $NETLIFY_AUTH_TOKEN" \
  "https://api.netlify.com/api/v1/sites/{site_id}"

# Check deploys (latest 5)
curl -s -H "Authorization: Bearer $NETLIFY_AUTH_TOKEN" \
  "https://api.netlify.com/api/v1/sites/{site_id}/deploys?page=1&per_page=5"

# Check environment variables
curl -s -H "Authorization: Bearer $NETLIFY_AUTH_TOKEN" \
  "https://api.netlify.com/api/v1/sites/{site_id}/env"

Read the full file on GitHub · 194 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.

  1. 7d ago First seen · 194 lines · 35 tokens per session scan A fde6ce714fa5

Subscribe to this mod's changes

deployment-inspection is a skill published in the GitHub repository S3YED/appie-kit (9 stars, last pushed 15d ago), licensed MIT. It adds 35 tokens to every session and 2,008 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

gcp-logs

Query GCP Cloud Logging for errors, service logs, and request traces. Use when investigating GCP-hosted services.

eveld/claude · 29 tokens

paperclip-dev

Develop and operate a local Paperclip instance — start and stop servers, pull updates from master, run builds and tests, manage worktrees, back up databases, and diagnose problems. Use whenever you need to work on the Paperclip codebase itself or keep a running instance healthy.

aimerdoux/wavex-os · 60 tokens

triage-issue

Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.

aden-hive/hive · 0 tokens

atmos-diagnostics

Atmos diagnostics: machine-readable JSONL event streams, diagnostics.enabled/file/includeoutput, subprocess start/end/output events, masking, and debugging Atmos execution.

cloudposse/atmos · 33 tokens

review-loop

Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…

sangrokjung/claude-forge · 100 tokens

wire-observability

Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.

danielvm-git/bigpowers · 53 tokens