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 skills add summarybotng/summarybot-ng --skill pentest-validationgit clone --depth 1 https://github.com/summarybotng/summarybot-ngWrote 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/summarybotng/summarybot-ng/pentest-validation)<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/pentest-validation"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/pentest-validation/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.
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/pentest-validation"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/pentest-validation.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00057 | $0.02595 |
| Opus 5.5 | $0.00023 | $0.01038 |
| Sonnet 5.5 | $0.00011 | $0.00519 |
| Haiku 4.5 | $0.00006 | $0.00260 |
Grade B, and why
pentest-validation scanned grade B 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 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.
| Internal URL | User-controlled URL fetch | `http://169.254.169.254` | Cloud metadata extraction | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pentest Validation
<default_to_action> When validating security findings:
- REQUIRE explicit authorization for target URL
- SCAN with qe-security-scanner (SAST + dependency + secrets)
- ANALYZE with qe-security-reviewer + qe-security-auditor (parallel)
- VALIDATE with qe-pentest-validator (graduated exploitation, parallel per vuln type)
- REPORT only confirmed findings with PoC evidence ("No Exploit, No Report")
- UPDATE exploit playbook with new patterns
Quality Gates:
- Authorization confirmed before ANY exploitation
- Target URL is staging/dev (NOT production)
- Budget cap enforced ($15 default)
- Time cap enforced (30 min default)
- All exploitation attempts logged </default_to_action>
Quick Reference Card
The 4-Phase Pipeline
| Phase | Agent(s) | Purpose | Parallelism |
|---|---|---|---|
| 1. Recon | qe-security-scanner | SAST, DAST, dependency scan, secrets | Internal parallel |
| 2. Analysis | qe-security-reviewer + qe-security-auditor | Code review + compliance check | Both in parallel |
| 3. Validation | qe-pentest-validator | Graduated exploit validation | Per-vuln-type parallel |
| 4. Report | qe-quality-gate | "No Exploit, No Report" filter | Sequential |
Graduated Exploitation Tiers
| Tier | Handler | Cost | Latency | Use When |
|---|---|---|---|---|
| 1 | Agent Booster (WASM) | $0 | <1ms | Code pattern is conclusive (eval, innerHTML, hardcoded creds) |
| 2 | Haiku | $0.0002 | ~500ms | Need payload test against live target |
| 3 | Sonnet/Opus | $0.003-$0.015 | 2-5s | Full exploit chain with data proof |
When to Use This Skill
| Scenario | Tier | Estimated Cost |
|---|---|---|
| PR security review (source only) | 1 | $0 |
| Pre-release validation (staging) | 1-2 | $1-5 |
| Full pentest validation | 1-3 | $5-15 |
| Compliance audit evidence | 1-3 | $5-15 |
Configuration
pentest:
target_url: https://staging.app.com # REQUIRED for Tier 2-3
source_repo: ./src # REQUIRED for Tier 1+
exploitation_tier: 2 # 1=pattern-only, 2=payload-test, 3=full-exploit
vuln_types: # Which pipelines to run
- injection # SQL, NoSQL, command injection
- xss # Reflected, stored, DOM XSS
- auth # Auth bypass, session, JWT
- ssrf # URL scheme abuse, metadata
max_cost_usd: 15 # Budget cap per run
timeout_minutes: 30 # Time cap per run
require_authorization: true # MUST confirm target ownership
no_production: true # Block production URLs
production_patterns: # URL patterns to block
- "*.prod.*"
- "api.*"
- "www.*"
What ships with it
3 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.
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 · 269 lines · 57 tokens per session scan B 856bfd88319a
pentest-validation is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 2,595 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (cloud metadata endpoint). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
performing-api-security-testing-with-postman
Uses Postman to perform structured API security testing by building collections that test for OWASP API Security Top 10 vulnerabilities including authentication bypass, authorization flaws, injection, and data exposure. The tester creates environments with multiple user roles, writes test scripts for automated…
accessibility-testing
WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.
database-testing
Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance. Use when testing data persistence, ensuring referential integrity, or validating database migrations.
chaos-engineering-resilience
Chaos engineering principles, controlled failure injection, resilience testing, and system recovery validation. Use when testing distributed systems, building confidence in fault tolerance, or validating disaster recovery.
compatibility-testing
Cross-browser, cross-platform, and cross-device compatibility testing ensuring consistent experience across environments. Use when validating browser support, testing responsive design, or ensuring platform compatibility.
playbook-webapp
Web application pentest methodology + ROUTER to the per-vuln-class web skills. Load at the START of systematic web testing to get the phase flow (recon → map → test-by-OWASP-class → prove → report) and pick which web- skill to load for each surface. Use on any web app / HTTP API engagement.