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.
npx agentmods add skills/thapr0digy/skills/enum-webnpx skills add thapr0digy/skills --skill enum-webgit clone --depth 1 https://github.com/thapr0digy/skillsWrote 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.
[](https://agentmods.dev/skills/thapr0digy/skills/enum-web)<a href="https://agentmods.dev/skills/thapr0digy/skills/enum-web"><img src="https://agentmods.dev/badge/skills/thapr0digy/skills/enum-web.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00039 | $0.14353 |
| Opus 5 | $0.00019 | $0.07176 |
| Sonnet 5 | $0.00008 | $0.02871 |
| Haiku 4.5 | $0.00004 | $0.01435 |
Grade A, and why
enum-web scanned grade A with 2 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 3d 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.
Sends data to an external URLlowData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
--arg command "HTTP_STATUS=$(curl -sk -X POST \"$GRAPHQL_URL\" -H \"Content-Type: application/json\" -d \"$INTROSPECTION_QUERY\" -w \"%{http_code}\" -o \"$GRAPHQL_OUT\" 2>/dev/null)" \ Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
TARGET_HOST=$(python3 -c "from urllib.parse import urlparse; print(urlparse('$WEB_URL').hostname)") How it starts
The opening of the file, as written. The whole thing — 1,292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@pentest-core/skills/shared/engagement-resolver.md @pentest-core/skills/shared/scope-validator.md @pentest-core/skills/shared/activity-log.md @pentest-core/skills/shared/safe-auth-validation.md
/enum-web — Web Application Security Assessment
You are conducting comprehensive security assessment of web applications and APIs to evaluate security controls, identify vulnerabilities, and validate compliance with web security standards. Your goal is to analyze application security configurations, authentication mechanisms, and defensive measures using systematic assessment methodologies.
Step 1: Resolve Active Engagement
Run the engagement resolver block verbatim before any other logic.
# --- Engagement Resolver ---
ENGAGEMENT_JSON=$(cat ~/.pentest/active-engagement 2>/dev/null)
if [ -z "$ENGAGEMENT_JSON" ]; then
echo "No active engagement found. Run /pentest-init or /pentest-switch." >&2
exit 1
fi
if [ ! -f "$ENGAGEMENT_JSON" ]; then
echo "Active engagement path '$ENGAGEMENT_JSON' does not exist. Run /pentest-switch." >&2
exit 1
fi
ENGAGEMENT_ID=$(jq -r '.engagement_id' "$ENGAGEMENT_JSON")
OUTPUT_DIR=$(jq -r '.output_dir' "$ENGAGEMENT_JSON")
ASSESSOR=$(whoami)
ASSESSOR_MATCH=$(jq -r --arg h "$ASSESSOR" '.security assessors[] | select(.handle == $h) | .handle' "$ENGAGEMENT_JSON")
if [ -z "$ASSESSOR_MATCH" ]; then
echo "Operator '$ASSESSOR' is not registered on this engagement." >&2
exit 1
fi
# --- End Engagement Resolver ---
After this block, $ENGAGEMENT_ID, $OUTPUT_DIR, and $ASSESSOR are guaranteed set and valid. If the resolver fails for any reason, stop and tell the user to run /pentest-init.
Step 2: Parse Arguments and Determine Targets
Accepted input
- URL — e.g.,
https://app.acme.comorhttp://10.0.0.1:8080 - No argument — fall back to most recent active recon output
ARG="${1:-}"
if [ -n "$ARG" ]; then
WEB_TARGETS=("$ARG")
elif ls "${OUTPUT_DIR}/recon/active-"*.json > /dev/null 2>&1; then
RECON_FILE=$(ls -t "${OUTPUT_DIR}/recon/active-"*.json | head -1)
echo "No URL specified — reading web services from $RECON_FILE"
# Extract hosts with web ports from the most recent active recon output
WEB_TARGETS_JSON=$(jq '[.hosts[] | {ip, hostnames, ports: [.ports[] | select(.category == "web")]} | select(.ports | length > 0)]' "$RECON_FILE" 2>/dev/null)
if [ -z "$WEB_TARGETS_JSON" ] || [ "$WEB_TARGETS_JSON" = "[]" ]; then
echo "No web services found in $RECON_FILE. Provide a URL: /enum-web <url>" >&2
exit 1
fi
# Build URL list from recon data
mapfile -t WEB_TARGETS < <(echo "$WEB_TARGETS_JSON" | jq -r '.[] | .ip as $ip | .ports[] | (if .tls then "https" else "http" end) + "://" + $ip + ":" + (.port | tostring)')
else
echo "No URL provided and no active recon data found." >&2
echo "Provide a URL: /enum-web <url>" >&2
exit 1
fi
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.
- 3d ago First seen · 1,292 lines · 39 tokens per session scan A 6b27f361ab16
enum-web is a skill published in the GitHub repository thapr0digy/skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 14,353 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…