mcpbeat Sign in

Common Dast Tooling Agent Skill

Standardize dynamic application security testing for backend APIs, frontend web apps, and mobile clients. Covers ZAP, Nuclei, Nikto, sqlmap, ffuf, browser automation, mobile proxy interception, and AI-driven curl probes. Use when advising on or running dynamic security scans on local/staging environments.

2k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
536
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill common-dast-tooling

What comes with it

4 639 bytes besides the instruction
references/implementation.md

The instruction itself

12 sections, as written by the author

DAST Tooling Standard

Priority: P1 (HIGH)

Always-Apply Rules

  • No Scanning Production: Never run DAST tools against live production environments. Use local or staging replicas only.
  • No Uncapped Scans: Always set max-depth or max-duration to avoid infinite loops on dynamic routes.
  • No Anonymous Probing: Use authenticated headers (Authorization) to test protected surfaces, not public ones.
  • No Mobile on Real Devices in Prod: Use emulators/simulators for mobile interception testing.

1. Backend / API Tools

Scanner Tools

See implementation guide for setup commands.

  • Nuclei: Fast, template-based CVE/misconfiguration scanning.
  • ZAP-CLI: Deep spidering for SQLi, XSS, CSRF, session issues.
  • Nikto: Server configuration audit (version disclosure, headers).
  • sqlmap: Automated SQL injection detection and exploitation (suggest only — human confirms).
  • ffuf / feroxbuster: Content discovery and endpoint fuzzing.

API-Specific Probing

  • GraphQL: Introspection query, nested query depth attack, field suggestion enumeration.
  • gRPC: grpcurl for service enumeration and method probing.
  • WebSocket: Connection hijacking, message injection testing.

2. Frontend / Web Tools

  • Browser DevTools: Network tab for auth token leakage, console for client-side errors.
  • Playwright/Puppeteer (suggested): Automated DOM XSS detection, form submission, CSRF testing.
  • Lighthouse: Security/performance audit (CSP, HTTPS, mixed content).
  • CSP Evaluator: Validate Content-Security-Policy headers.

3. Mobile Interception Tools

  • mitmproxy / Burp Suite: Proxy mobile traffic for API inspection.
  • Frida: Runtime instrumentation for cert pin bypass, biometric bypass, jailbreak detection bypass.
  • adb / xcrun simctl: Device-level inspection, deep link testing, storage extraction.
  • Objection: Mobile runtime exploration (iOS/Android).

4. AI-Driven curl Probing (Manual Fallback)

When automated tools unavailable, generate targeted curl probes:

  • Bypassing Guards: Probe with manipulated headers (X-Forwarded-For, X-Custom-Auth).
  • Data Leakage: Request /metrics, /health, .git, /.env, /api-docs.
  • Parameter Tampering: Modify payload types (String→Object), inject large payloads.
  • JWT Manipulation: Test with expired token, no token, modified claims.

See implementation guide for all commands.

Scoring Impact

| Finding | Severity | Deduction |

|---|---|---|

| Unauthenticated access to private data | P0 | -25 |

| Successful SQLi/RCE via probe | P0 | -20 |

| Mobile API interception (no cert pin) | P1 | -15 |

| DOM XSS confirmed via browser | P1 | -10 |

| Info Leakage (Server versions/Env vars) | P1 | -10 |

| Missing security headers (CSP/HSTS) | P2 | -5 |

Anti-Patterns

  • No relying solely on static analysis: Pentesting MUST include dynamic execution feedback.
  • No ignoring non-web protocols: Check Docker ports, SSH banners, gRPC/RMQ listeners.
  • No skipping mobile: If mobile app exists, proxy its traffic and inspect API calls.

References

Other skills for the same job

different authors, same section of the catalogue
Webapp Testing
by anthropics
vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts
Azure Microsoft Playwright Testing Ts
by lingxling
×1

Run Playwright tests at scale with cloud-hosted browsers and integrated Azure portal reporting.

2k tokens
Chrome Devtools
by christophacham
×1

Browser debugging, performance profiling, and automation via Chrome DevTools MCP. Use when user says "debug this page", "take a screenshot", "check network requests", "profile performance", "inspect console errors", or "analyze page load". Do NOT use for full E2E test suites (use playwright-skill) or non-browser debugging.

1k tokens
QA
by browser-use

QA-test a website or web app and return a 1-5 quality score (5 = flawless, 1 = broken) with evidence. Use when the user wants to test, QA, evaluate, score, or "check how good" a site, page, flow, or app — including a local dev server (e.g. "qa test localhost:5173", "does the checkout work?", "rate this landing page"). Drives a real Browser Use cloud browser, tunneling localhost automatically.

9k tokens
Playwright Component Testing
by microsoft
vendor

Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.

8k tokens scripts
Browser Testing With Devtools
by addyosmani

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

4k tokens
Browser Harness
by browser-use

Always use browser-harness for any web interaction: automation, scraping, testing, or site/app work.

493k tokens scripts
Help Center UI Test
by Automattic

Run a browser-based UI review of the WordPress.com Help Center across multiple surfaces, looking for visual and behavioral issues. Use when asked to test the Help Center UI.

2k tokens

How to use it

Copy the folder

Take hoangnguyen0403/common-dast-tooling from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.