/common-pentest-methodology
PTES-aligned penetration testing methodology for backend, frontend, and mobile. Provides attack taxonomy, exploit techniques per vulnerability class, and platform-specific test matrices. Use when executing pentest workflow, planning security assessments, mapping attack surfaces,
$ npx -y skills add hoangnguyen0403/agent-skills-standard --skill common-pentest-methodology --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/common-pentest-methodology
Context preview
The summary Claude sees to decide when to auto-load this skill.
PTES-aligned penetration testing methodology for backend, frontend, and mobile. Provides attack taxonomy, exploit techniques per vulnerability class, and platform-specific test matrices. Use when executing pentest workflow, planning security assessments, mapping attack surfaces,
SKILL.md
common-pentest-methodology.SKILL.mdname: common-pentest-methodology
description: PTES-aligned penetration testing methodology for backend, frontend, and mobile. Provides attack taxonomy, exploit techniques per vulnerability class, and platform-specific test matrices. Use when executing pentest workflow, planning security assessments, mapping attack surfaces, or building threat models.
metadata:
triggers:
keywords:
- pentest
- penetration test
- red team
- attack surface
- threat model
- PTES
- security assessment
- exploit
- hacker scorePenetration Testing Methodology (PTES-Aligned)
**Priority: P0 (CRITICAL)**
Always-Apply Rules
- **No Exploit = No Report**: Every finding requires reproducible Proof-of-Concept. Hypotheses without PoC are discarded.
- **No Production Testing**: All dynamic probes target local/staging only. Confirm authorization before Phase 1.
- **No Single-Platform Bias**: Assess backend, frontend, AND mobile surfaces when in-scope.
Workflow
Load alongside `/pentest` workflow. Provides methodology backbone for all 7 phases.
1. **Scope** → Define test mode (whitebox/greybox/blackbox), platforms, exclusions. 2. **Recon** → Build asset inventory per platform. See [platform-recon](references/platform-recon.md). 3. **Threat Model** → Rank endpoints by risk. See [threat-modeling](references/threat-modeling.md). 4. **Analyze** → Run vulnerability matrix across all domains. Load `common-owasp`, `common-security-audit`, `common-dast-tooling`. 5. **Exploit** → Validate each finding with PoC. See [exploit-techniques](references/exploit-techniques.md). 6. **Post-Exploit** → Assess blast radius, lateral movement, privilege escalation. 7. **Report** → Audit-grade output with CVSS scoring. See [report-template](references/report-template.md) and [compliance-mapping](references/compliance-mapping.md).
Platform Coverage Matrix
| Domain | Backend/API | Frontend/Web | Mobile (iOS/Android) | |---|---|---|---| | Injection | SQLi, CMDi, NoSQLi, LDAPi | Template injection, DOM sinks | Content provider SQLi, Intent injection | | XSS | Response encoding | DOM XSS, `innerHTML`, framework bypasses | WebView `loadUrl`, JavaScript bridges | | Auth | JWT, OAuth, Session, MFA | Token storage, session management | Keychain/Keystore, biometric bypass | | AuthZ | BOLA/IDOR, BFLA, Mass Assignment | Client-side role gates | Local permission checks without server | | SSRF | HTTP client + user URL | SSR with user-supplied URL | Custom scheme fetching arbitrary URLs | | Business Logic | Race conditions, workflow bypass | Client-only validation, price tamper | IAP bypass, receipt validation skip | | Crypto | Weak hash, missing TLS | HTTP calls, weak CSP | Missing cert pin, cleartext traffic | | Config | CORS, debug mode, headers | Source maps, debug flags in prod | `debuggable=true`, ATS exceptions | | Deps/SCA | `npm audit`, `pip-audit`, `cargo audit` | Bundle vuln analysis | `pod audit`, Gradle dependency scan | | Secrets | Entropy + regex + liveness | Secrets in JS bundles | Keys in BuildConfig/Info.plist | | LLM/AI | Prompt injection, excessive agency | Output to DOM sinks | Agent tools without confirmation |
Continuous & Compliance Execution
- **Continuous Testing**: Execute Delta scans on PRs or Replay regression PoCs. See [continuous-pentest](references/continuous-pentest.md).
- **Compliance Mapping**: Map findings to SOC 2, ISO 27001, PCI DSS, or OWASP MASVS. See [compliance-mapping](references/compliance-mapping.md).
Anti-Patterns
- **No "scan and dump"**: Raw tool output not a pentest. Correlate findings across SAST + DAST + manual.
- **No severity inflation**: Theoretical risk without exploit evidence ≠ confirmed vulnerability.
- **No happy-path-only**: Test error states, edge cases, race conditions, not just golden flow.
References
- [Platform Reconnaissance](references/platform-recon.md) — Phase 1 recon commands per platform
- [Threat Modeling Guide](references/threat-modeling.md) — Phase 2 attack surface prioritization
- [Exploit Techniques](references/exploit-techniques.md) — Phase 4 PoC construction per vuln class
- [Report Template](references/report-template.md) — Phase 6 audit-grade report format
- [OWASP Mobile Top 10](references/owasp-mobile.md) — Mobile vulnerability detection
- [Compliance Mapping](references/compliance-mapping.md) — SOC 2, ISO 27001, PCI DSS mapping
- [Continuous Pentesting](references/continuous-pentest.md) — CI/CD integration and Delta testing
Read more
name: common-pentest-methodology
description: PTES-aligned penetration testing methodology for backend, frontend, and mobile. Provides attack taxonomy, exploit techniques per vulnerability class, and platform-specific test matrices. Use when executing pentest workflow, planning security assessments, mapping attack surfaces, or building threat models.
metadata:
triggers:
keywords:
- pentest
- penetration test
- red team
- attack surface
- threat model
- PTES
- security assessment
- exploit
- hacker scorePenetration Testing Methodology (PTES-Aligned)
**Priority: P0 (CRITICAL)**
Always-Apply Rules
- **No Exploit = No Report**: Every finding requires reproducible Proof-of-Concept. Hypotheses without PoC are discarded.
- **No Production Testing**: All dynamic probes target local/staging only. Confirm authorization before Phase 1.
- **No Single-Platform Bias**: Assess backend, frontend, AND mobile surfaces when in-scope.
Workflow
Load alongside `/pentest` workflow. Provides methodology backbone for all 7 phases.
1. **Scope** → Define test mode (whitebox/greybox/blackbox), platforms, exclusions. 2. **Recon** → Build asset inventory per platform. See [platform-recon](references/platform-recon.md). 3. **Threat Model** → Rank endpoints by risk. See [threat-modeling](references/threat-modeling.md). 4. **Analyze** → Run vulnerability matrix across all domains. Load `common-owasp`, `common-security-audit`, `common-dast-tooling`. 5. **Exploit** → Validate each finding with PoC. See [exploit-techniques](references/exploit-techniques.md). 6. **Post-Exploit** → Assess blast radius, lateral movement, privilege escalation. 7. **Report** → Audit-grade output with CVSS scoring. See [report-template](references/report-template.md) and [compliance-mapping](references/compliance-mapping.md).
Platform Coverage Matrix
| Domain | Backend/API | Frontend/Web | Mobile (iOS/Android) | |---|---|---|---| | Injection | SQLi, CMDi, NoSQLi, LDAPi | Template injection, DOM sinks | Content provider SQLi, Intent injection | | XSS | Response encoding | DOM XSS, `innerHTML`, framework bypasses | WebView `loadUrl`, JavaScript bridges | | Auth | JWT, OAuth, Session, MFA | Token storage, session management | Keychain/Keystore, biometric bypass | | AuthZ | BOLA/IDOR, BFLA, Mass Assignment | Client-side role gates | Local permission checks without server | | SSRF | HTTP client + user URL | SSR with user-supplied URL | Custom scheme fetching arbitrary URLs | | Business Logic | Race conditions, workflow bypass | Client-only validation, price tamper | IAP bypass, receipt validation skip | | Crypto | Weak hash, missing TLS | HTTP calls, weak CSP | Missing cert pin, cleartext traffic | | Config | CORS, debug mode, headers | Source maps, debug flags in prod | `debuggable=true`, ATS exceptions | | Deps/SCA | `npm audit`, `pip-audit`, `cargo audit` | Bundle vuln analysis | `pod audit`, Gradle dependency scan | | Secrets | Entropy + regex + liveness | Secrets in JS bundles | Keys in BuildConfig/Info.plist | | LLM/AI | Prompt injection, excessive agency | Output to DOM sinks | Agent tools without confirmation |
Continuous & Compliance Execution
- **Continuous Testing**: Execute Delta scans on PRs or Replay regression PoCs. See [continuous-pentest](references/continuous-pentest.md).
- **Compliance Mapping**: Map findings to SOC 2, ISO 27001, PCI DSS, or OWASP MASVS. See [compliance-mapping](references/compliance-mapping.md).
Anti-Patterns
- **No "scan and dump"**: Raw tool output not a pentest. Correlate findings across SAST + DAST + manual.
- **No severity inflation**: Theoretical risk without exploit evidence ≠ confirmed vulnerability.
- **No happy-path-only**: Test error states, edge cases, race conditions, not just golden flow.
References
- [Platform Reconnaissance](references/platform-recon.md) — Phase 1 recon commands per platform
- [Threat Modeling Guide](references/threat-modeling.md) — Phase 2 attack surface prioritization
- [Exploit Techniques](references/exploit-techniques.md) — Phase 4 PoC construction per vuln class
- [Report Template](references/report-template.md) — Phase 6 audit-grade report format
- [OWASP Mobile Top 10](references/owasp-mobile.md) — Mobile vulnerability detection
- [Compliance Mapping](references/compliance-mapping.md) — SOC 2, ISO 27001, PCI DSS mapping
- [Continuous Pentesting](references/continuous-pentest.md) — CI/CD integration and Delta testing
The portable SDLC standards layer for AI coding agents. Sync once, then work in your own runtime.
Repo: hoangnguyen0403/agent-skills-standard
Other skills on agent-skills-standard.
- /android-agp-upgrade
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Open skill - /android-architecture
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow
Open skill - /android-background-work
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Open skill - /android-compose-migration
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Open skill - /android-compose
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Open skill - /android-concurrency
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes,
Open skill

