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 agentmods add skills/fb0sh/pentester/pentester-setup-toolsnpx skills add fb0sh/pentester --skill pentester-setup-toolsgit clone --depth 1 https://github.com/fb0sh/pentesterWhat 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 | $0.00055 | $0.00743 |
| Opus 5 | $0.00028 | $0.00371 |
| Sonnet 5 | $0.00011 | $0.00149 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
pentester-setup-tools 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 2d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pentester-setup-tools
Run once before an engagement. Three layers: framework, wordlists, tools.
1. Framework deps
| Check | Fix |
|---|---|
| Playwright / Chromium | cd .agents/skills/pentester-playwright && npm run setup |
Kali image (scan_env=docker) |
docker pull kalilinux/kali-rolling |
| Schema validator | node .agents/schema/validate-target-schema.js prints usage |
2. Wordlists — PentesterSpecialDict (git submodule)
Dicts live at .agents/wordlists/PentesterSpecialDict/ (upstream
evilc0deooo/PentesterSpecialDict).
Needs network on first pull; safe to re-run (idempotent).
node .agents/wordlists/ensure.js
# optional refresh: node .agents/wordlists/ensure.js --update
# preflight only: node .agents/wordlists/ensure.js --check
Docker: mount .agents/wordlists → /wordlists (see schema/env.md).
Before gobuster/ffuf/hydra/sqlmap fuzz, if --check fails → run ensure.
3. Pentest tools — resolve first, provision on demand
Engagement runtime should query the capability catalog instead of installing everything:
node .agents/tools/resolve.js --id ${ID} --phase <phase> --scan-env <host-kali|docker> --signals "..."
node .agents/tools/ensure.js --scan-env <host-kali|docker> --id ${ID} --dry-run <selected-tool>
Only replace --dry-run with --install after the tool is selected. Kali apt candidates and the curated DotSlash set share this interface.
Optional pre-provision of the curated DotSlash set
The maintenance command below installs DotSlash, fills the needs-gen hashes, and lands all 11 pinned tools
(subfinder naabu httpx EHole dismap dddd nuclei afrog xray DefaultHound fscan) for the
current scan_env. Needs network.
# host-kali — tools on the host (dotslash → ~/.local/bin by default)
bash .agents/tools/provision.sh --scan-env host-kali all
# docker — inside kali-target-${ID} (container must already be running)
bash .agents/tools/provision.sh --scan-env docker --id ${ID} all
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.
- 2d ago First seen · 67 lines · 55 tokens per session scan A 9e27a03f80cb
pentester-setup-tools is a skill published in the GitHub repository fb0sh/pentester (23 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 743 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
transilience-report-style
Threat Intelligence Report Design System — ReportLab-based PDF generation for A4 reports with Transilience branding, typography, and layout standards.
firewall-review
Evidence-safe firewall ruleset audit reference specification — 22 documented detector patterns (17 vendor-agnostic plus 5 FortiGate-specific), a 15-check semantic catalogue, CIS Fortinet FortiGate Benchmark guidance, a custom customer-policy benchmark, and consolidated network-team Excel profiles including grouped…
pentest-engagement
Run a professional penetration engagement OR a network vulnerability scan from a scope. WEB mode (apex domains / app URLs) — mandatory surface expansion, systematic OWASP attack-class coverage, reversible active exploitation, authoritative validation, Transilience PDF. NETWORK mode (a list of IPs/CIDRs, e.g. 1500…
attack-path-stitcher
Stitches confirmed single-asset findings into multi-hop attack paths across the organization. Builds a graph where nodes are assets and edges are confirmed exploit hops citing the findings that enable them.
coordination
Pentest coordination — orchestrates executor and validator agents with context-controlled spawning. Entry point for all engagements.
hackerone
HackerOne bug bounty automation - parses scope CSVs, deploys parallel pentesting agents per asset, validates PoCs, and generates platform-ready submission reports.