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 HoangNguyen0403/agent-skills-standard --skill common-pentest-methodologygit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/common-pentest-methodology)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-pentest-methodology"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-pentest-methodology/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/hoangnguyen0403/agent-skills-standard/common-pentest-methodology"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-pentest-methodology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 52 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 53 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.01068 |
| Opus 5 | $0.00028 | $0.00534 |
| Sonnet 5 | $0.00011 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
common-pentest-methodology scanned grade A with 0 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 12d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
- Scope → Define test mode (whitebox/greybox/blackbox), platforms, exclusions.
- Recon → Build asset inventory per platform. See platform-recon.
- Threat Model → Rank endpoints by risk. See threat-modeling.
- Analyze → Run vulnerability matrix across all domains. Load
common-owasp,common-security-audit,common-dast-tooling. - Exploit → Validate each finding with PoC. See exploit-techniques.
- Post-Exploit → Assess blast radius, lateral movement, privilege escalation.
- Report → Audit-grade output with CVSS scoring. See report-template and compliance-mapping.
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 |
What ships with it
7 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.
- 12d ago First seen · 75 lines · 57 tokens per session scan A b296f27b2f91
common-pentest-methodology is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 1,068 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
elite-engineer
The operating system for elite software engineering in TypeScript, React, and Next.js. Enforces the cognitive models, architecture laws, type-level patterns, component design, visual standards, and performance mandates that separate exceptional software from the ordinary — grounded in named sources (Torvalds…
oma-frontend
Frontend specialist for React, Next.js, Angular, TypeScript with FSD-lite architecture, shadcn/ui, and design system alignment. Use for UI, component, page, layout, CSS, Tailwind, shadcn, Angular, and RxJS work.
design-patterns
Frontend design patterns with React 19.2 and TypeScript 6 examples (Composition, Compound Components, Custom Hooks, Render Props, HOC, State Machines). Use when user asks "implement pattern", "use composition", or when designing reusable components.
react-nextjs
React 19.2 + Next.js 16 development - Server Components, Cache Components, proxy.ts, View Transitions, App Router, TypeScript 6, and Tailwind CSS v4. Use when building frontend apps, creating components, or asking "how do I set up X?".
code-quality
Comprehensive frontend code review for TypeScript 6 and React 19.2 — clean code principles, component patterns, type safety, accessibility, and performance. Use when user says "review code", "refactor", "check this PR", or before merging changes.
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.