What is playbook-methodology?

A reference for planning authorized security assessments, including testing standards, scope, evidence handling, cleanup, and rules of engagement. Rules of engagement are the written limits and permissions for a test.

Use it at the start of a penetration test to choose a methodology, confirm authorization and scope, handle third parties, and define allowed actions.

It helps prevent testing outside the agreed target or using techniques that lack written approval, while keeping findings consistent and auditable.

playbook-methodology — Skill for Claude Code and Codex by s0ld13rr

Install

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.

Any agent

npx skills add s0ld13rr/pentestcode --skill methodology

Clone the repo

git clone --depth 1 https://github.com/s0ld13rr/pentestcode

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/s0ld13rr/pentestcode/methodology/github.svg)](https://agentmods.dev/skills/s0ld13rr/pentestcode/methodology)

Your own site

<a href="https://agentmods.dev/skills/s0ld13rr/pentestcode/methodology"><img src="https://agentmods.dev/badge/skills/s0ld13rr/pentestcode/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/s0ld13rr/pentestcode/methodology"><img src="https://agentmods.dev/badge/skills/s0ld13rr/pentestcode/methodology.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 663 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00048	$0.00663
Opus 5.5	$0.00019	$0.00265
Sonnet 5.5	$0.00010	$0.00133
Haiku 4.5	$0.00005	$0.00066

Measured 14d ago against content hash 48dd83fa1bef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

playbook-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 14d 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.

skills/playbooks/methodology/SKILL.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Methodology & Rules of Engagement

Framework map (pick per engagement type)

Framework	Use when
PTES	Full-scope pentest — the 7-phase spine (intel → recon → mapping → vuln → exploit → post-ex → report)
OWASP Testing Guide	Web/API focus — test cases per vuln class
NIST SP 800-115	Client requires a recognized US standard / structured technical assessment
OSSTMM	Metrics-driven assessment, need auditable coverage percentages
MITRE ATT&CK	Map findings to real adversary TTPs — report impact as "an attacker would do X"

BEFORE any action — non-negotiable

Written authorization exists, signed by someone who can authorize the target. Verbal = no test.
Scope: exact IPs/domains/ranges, exclusions, test window, allowed techniques. Feed to scope_check — every tool invocation checks against it.
Rules of engagement: scan rates, DoS limits, social-engineering allowed?, physical allowed?, data handling clause, emergency contact.
Third parties: cloud shared-responsibility boundaries, subsidiaries, partners' infra — out of scope unless explicitly named.
Legal frame: client contract + local law (Convention Budapest / national cybercrime law) supersedes any methodology.

During the test

Log every action (command, timestamp, target) — your log is the defense if something breaks.
Rate-limit scanners and brute force; assume any outage is YOURS until proven otherwise.
Collect the minimum data needed to prove impact; encrypt findings at rest; never exfil real customer data to personal storage.
Compromise of an out-of-scope system, even accidental: stop, secure it, disclose to client immediately.
Out-of-band callbacks: use your own infrastructure (interactsh/ollin), never third-party domains.

AFTER the test — cleanup

Remove: shells/backdoors, dropped files, created accounts, cron/persistence, SSH keys, test data injected.
Verify cleanup: re-check every host touched; note anything that cannot be removed safely (and why).
Revoke/deliver credentials found — do NOT reuse them post-engagement.

Read the full file on GitHub · 46 lines

Changes

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.

14d ago First seen · 46 lines · 48 tokens per session scan A 48dd83fa1bef

Subscribe to this mod's changes

playbook-methodology is a skill published in the GitHub repository s0ld13rr/pentestcode (929 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 663 once invoked, about $0.0002 per session on Opus 5.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-10-24.

Legal and compliance Security ai-agents ai-security ai-security-tool anthropic gpt openai scope_check

playbook-methodology next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
playbook-methodologys0ld13rr/pentestcode	Skill	929	yesterday	MIT	A	48	Claude Code, Codex
lictor-security-checkRaffa-jarrl/Lictor-AI	Skill	18	3mo ago	Apache-2.0	A	135	Claude Code
lictor-rotateRaffa-jarrl/Lictor-AI	Skill	18	3mo ago	Apache-2.0	A	80	Claude Code
lictor-explainRaffa-jarrl/Lictor-AI	Skill	18	3mo ago	Apache-2.0	A	56	Claude Code
compliancefrumu-ai/tandem	Skill	125	1mo ago	none	A	51	Claude Code, Codex
legal-risk-assessmentfrumu-ai/tandem	Skill	125	1mo ago	none	A	50	Claude Code, Codex
finance-sox-testingfrumu-ai/tandem	Skill	125	1mo ago	none	A	18	Claude Code, Codex