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-knowledge-importnpx skills add fb0sh/pentester --skill pentester-knowledge-importgit 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.00033 | $0.00480 |
| Opus 5 | $0.00016 | $0.00240 |
| Sonnet 5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
pentester-knowledge-import 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.
What it actually says
Knowledge Import (maintainer factory)
Do not invoke during PTES phases. Runtime → pentester-knowledge-base + LOOKUP.md / bin/lookup.js.
CLI interface (what actually runs)
node .agents/skills/pentester-knowledge-import/import.js --stage status
node .agents/skills/pentester-knowledge-import/import.js --stage check
node .agents/skills/pentester-knowledge-import/import.js --stage pointers
| Stage | Implementation |
|---|---|
status |
Archive root / size hints / checkpoint |
check |
Locality seals (tier-2 not in PTES-INDEX surface) |
pointers |
Ensure TIER2-CATALOG pointers |
raw / index / refine |
Checkpoint only — heavy I/O is operator-driven (not automated bulk) |
Do not pretend raw|index|refine are full import engines; they write checkpoint + remind SKILL steps.
Locality (preferred)
| Prefer | Avoid |
|---|---|
External pack: KNOWLEDGE_ARCHIVE_ROOT=/path/to/pack |
Growing multi-GB trees under .agents/knowledge/github-references/ |
In-repo: TIER2-CATALOG.md pointers only |
Phase bags listing archive paths |
Checkpoint: .agents/knowledge/_import-checkpoint.md (gitignored).
Operator stages (manual)
- Raw — import readable text under archive root; sanitize; checkpoint
- Index — per-repo IMPORT-INDEX / ASSETS-MANIFEST; not PTES-INDEX
- Refine — promote methods via
pentester-knowledge-base+ PTES-INDEX only (never bulk archive into INDEX.md)
Then: import.js --stage check + lookup.js --check-index.
Rules
- Prefer external archive root
- High-risk material: Authorized/Training/Research only
- PTES phases never preload tier-2 trees
What ships with it
1 file 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.
- 2d ago First seen · 49 lines · 33 tokens per session scan A cf7b988b20b1
pentester-knowledge-import is a skill published in the GitHub repository fb0sh/pentester (23 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 480 once invoked, about $0.0002 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
coordination
Pentest coordination — orchestrates executor and validator agents with context-controlled spawning. Entry point for all engagements.
skill-update
Skill creation, update and management — generates skill directory structure, validates against best practices, enforces line count limits. Use when creating, updating, or improving skills.
skill-prune
Identify and remove negative-ROI skill content — orphan files, never-read entries, duplicates, content reintroducing challenge-specific lore. Inverse of /skill-update. Use during quarterly maintenance or after the linter flags issues.
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…