Common Pentest Methodology logo

Common Pentest Methodology

Community
HoangNguyen0403
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, or building threat models.

Overview

PublisherHoangNguyen0403
Repositoryagent-skills-standard
Skill namecommon-pentest-methodology
Stars
573
Forks
166
Bundled files
7
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 7 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by HoangNguyen0403 on GitHub. Read the source before you install it.

Installation

Install the Common Pentest Methodology AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/.agents/skills/common/common-pentest-methodology
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git /tmp/agent-skills-standard
mkdir -p .claude/skills
cp -r /tmp/agent-skills-standard/.agents/skills/common/common-pentest-methodology .claude/skills/common-pentest-methodology
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Common Pentest Methodology in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Common Pentest Methodology on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Common Pentest Methodology is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Penetration 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.
  3. Threat Model → Rank endpoints by risk. See threat-modeling.
  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.
  6. Post-Exploit → Assess blast radius, lateral movement, privilege escalation.
  7. Report → Audit-grade output with CVSS scoring. See report-template and compliance-mapping.

Platform Coverage Matrix

DomainBackend/APIFrontend/WebMobile (iOS/Android)
InjectionSQLi, CMDi, NoSQLi, LDAPiTemplate injection, DOM sinksContent provider SQLi, Intent injection
XSSResponse encodingDOM XSS, innerHTML, framework bypassesWebView loadUrl, JavaScript bridges
AuthJWT, OAuth, Session, MFAToken storage, session managementKeychain/Keystore, biometric bypass
AuthZBOLA/IDOR, BFLA, Mass AssignmentClient-side role gatesLocal permission checks without server
SSRFHTTP client + user URLSSR with user-supplied URLCustom scheme fetching arbitrary URLs
Business LogicRace conditions, workflow bypassClient-only validation, price tamperIAP bypass, receipt validation skip
CryptoWeak hash, missing TLSHTTP calls, weak CSPMissing cert pin, cleartext traffic
ConfigCORS, debug mode, headersSource maps, debug flags in proddebuggable=true, ATS exceptions
Deps/SCAnpm audit, pip-audit, cargo auditBundle vuln analysispod audit, Gradle dependency scan
SecretsEntropy + regex + livenessSecrets in JS bundlesKeys in BuildConfig/Info.plist
LLM/AIPrompt injection, excessive agencyOutput to DOM sinksAgent tools without confirmation

Continuous & Compliance Execution

  • Continuous Testing: Execute Delta scans on PRs or Replay regression PoCs. See continuous-pentest.
  • Compliance Mapping: Map findings to SOC 2, ISO 27001, PCI DSS, or OWASP MASVS. See compliance-mapping.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Common Pentest Methodology AI skill do?

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.

Why use Common Pentest Methodology on TypingMind?

Because you install it once and use it with any model. Common Pentest Methodology is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Common Pentest Methodology in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/.agents/skills/common/common-pentest-methodology. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Common Pentest Methodology?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Common Pentest Methodology?

As many as you like. As long as a model supports skills, you can use Common Pentest Methodology with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Common Pentest Methodology AI skill free?

Yes. It is published on GitHub by HoangNguyen0403 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇