A controlled workflow for testing web applications for security weaknesses through reconnaissance, analysis, evidence-based exploitation, and reporting.

Use it for authorized penetration tests of running web applications, including finding, verifying, and documenting exploitable issues.

It keeps security testing within an approved scope and requires reproducible evidence before reporting a vulnerability.

web-pentest — Skill for Claude Code and Codex by sairam0424/MindForge

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 sairam0424/MindForge --skill web-pentest

Clone the repo

git clone --depth 1 https://github.com/sairam0424/MindForge

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sairam0424/mindforge/web-pentest/github.svg)](https://agentmods.dev/skills/sairam0424/mindforge/web-pentest)

Your own site

<a href="https://agentmods.dev/skills/sairam0424/mindforge/web-pentest"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/web-pentest/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sairam0424/mindforge/web-pentest"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/web-pentest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,223 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 3 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 91% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00070	$0.03223
Opus 5.5	$0.00028	$0.01289
Sonnet 5.5	$0.00014	$0.00645
Haiku 4.5	$0.00007	$0.00322

Measured 1mo ago against content hash a22f21709b9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

web-pentest scanned grade B with 3 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 1mo 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.

Cloud metadata endpointmediumServer-side request forgery

One request to 169.254.169.254 can return temporary IAM credentials.

4. **Cloud metadata is off by default.** Do not probe `169.254.169.254`,

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.

active scanning. Reading public pages with `curl` is fine; sending

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

2. **Inventory sinks** — every `execute(`, `os.system(`, `eval(`,

Origin

This is a copy

91% identical to web-pentest — 43 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agent/skills/web-pentest/SKILL.md · 333 lines

How it starts

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

Web Application Penetration Testing

A phased pentesting workflow for running web applications. Adapted from Shannon's pipeline (Keygraph, AGPL — concepts only, no code borrowed). Built around three rules:

No exploit, no report — every finding requires reproducible evidence.
Bounded scope — every active request goes against a target the operator pre-declared. Off-scope hosts are refused.
Bypass exhaustion before false-positive dismissal — a "blocked" payload is not a clean bill of health until you've tried the bypass set.

⚠️ Hard Guardrails — Read Before Every Engagement

Violating any of these invalidates the engagement and may be illegal.

Authorization gate. Before the first active scan in a session, you MUST confirm with the user, in writing, that they own or have written authorization to test the target. Record the acknowledgement in engagement/authorization.md (see template). No acknowledgement → no active scanning. Reading public pages with curl is fine; sending payloads is not.
Scope allowlist. Maintain engagement/scope.txt — one hostname or CIDR per line. Every nmap, curl, whatweb, browser navigation, or payload-bearing request MUST be against an entry in scope. If a target redirects you off-scope (3xx to a different host, a link in HTML), STOP and confirm with the user before following.
No production systems without paper. If the user hasn't told you "yes, prod is in scope and I have written sign-off," assume not. Default targets are staging, local docker, dedicated test instances.
Cloud metadata is off by default. Do not probe 169.254.169.254, metadata.google.internal, 100.100.100.200, [fd00:ec2::254], or equivalent unless the engagement explicitly includes SSRF-to-metadata as a goal AND the target is one you control. The agent's browser tool can reach these from inside your own infrastructure — don't.
Destructive payloads need approval. SQLi payloads that DROP/DELETE, filesystem-write SSTI, command injection with rm/shutdown/mkfs, anything that mutates beyond a single test row → ASK FIRST. The approval.py system catches some; don't rely on it alone.

Read the full file on GitHub · 333 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

1mo ago First seen · 333 lines · 70 tokens per session scan B a22f21709b9f

Subscribe to this mod's changes

web-pentest is a skill published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 3,223 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 3 findings (cloud metadata endpoint, makes network calls, runs shell commands). It is 91% identical to web-pentest, differing in 43 lines, and is treated as a copy.

Claude Code Security agentic-workflows ai-agents antigravity automation developer-tools

ciel-antigravity-lookup

Find Antigravity conversations on macOS by UUID or keyword.

jxoesneon/Ciel · 21 tokens

workspace-mirror

Sync and backup Antigravity IDE sessions, transcripts, SQLite database metadata, and brain artifacts locally into a structured workspace directory (.gemini-local/) with a rich interactive viewer.html page. Use this skill whenever the user mentions backups, workspace syncing, fswatch real-time mirroring, viewing…

ahadkhan9/workspace-mirror-skill · 82 tokens

web-pentest