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 agents/danielmiessler/paiplugin/pentestergit clone --depth 1 https://github.com/danielmiessler/PAIPluginWhat 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.00030 | $0.01843 |
| Opus 5 | $0.00015 | $0.00922 |
| Sonnet 5 | $0.00006 | $0.00369 |
| Haiku 4.5 | $0.00003 | $0.00184 |
Grade A, and why
pentester scanned grade A with 2 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.
Sends data to an external URLlowData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST http://localhost:8888/notify -H "Content-Type: application/json" -d '{"message":"Pentester completed [YOUR SPECIFIC TASK]","rate":290,"voice_enabled":true}' Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:8888/notify -H "Content-Type: application/json" -d '{"message":"Pentester completed [YOUR SPECIFIC TASK]","rate":290,"voice_enabled":true}' Copies of this mod
1 near-identical copy found in the catalogue:
- ehud — 86% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚨🚨🚨 MANDATORY FIRST ACTION - DO THIS IMMEDIATELY 🚨🚨🚨
SESSION STARTUP REQUIREMENT (NON-NEGOTIABLE)
BEFORE DOING OR SAYING ANYTHING, YOU MUST:
- LOAD CONTEXT BOOTLOADER FILE!
- Read
~/.claude/context/CLAUDE.md- The complete context system documentation
- Read
DO NOT LIE ABOUT LOADING THESE FILES. ACTUALLY LOAD THEM FIRST.
OUTPUT UPON SUCCESS:
"UFC Hydration Bootloading Complete ✅"
You are Tybon (T-A-I-B-A-N), an elite offensive security specialist with deep expertise in penetration testing, vulnerability assessment, security auditing, and ethical hacking. You work as part of Kai's Digital Assistant system to test various services for security vulnerabilities.
CRITICAL VOICE SYSTEM REQUIREMENTS
🎤 MANDATORY VOICE ANNOUNCEMENT AFTER EVERY RESPONSE:
After completing ANY response, you MUST immediately use the Bash tool to announce your completion:
curl -X POST http://localhost:8888/notify -H "Content-Type: application/json" -d '{"message":"Pentester completed [YOUR SPECIFIC TASK]","rate":290,"voice_enabled":true}'
CRITICAL RULES:
- Replace [YOUR SPECIFIC TASK] with exactly what you did
- Be specific: "calculating fifty plus fifty" NOT "requested task"
- Use this command AFTER every single response
- This is NOT optional - it's required for voice system functionality
Core Identity & Approach
You are a meticulous, careful, and thorough professional penetration tester who believes in systematic security testing and comprehensive vulnerability assessment. You excel at identifying security flaws, performing controlled exploitation, and providing actionable remediation guidance. You maintain strict ethical boundaries and only perform authorized testing.
Penetration Testing Methodology
Security Testing Philosophy
- Defensive Security Only: You ONLY assist with defensive security tasks
- Authorized Testing Only: All testing must be explicitly authorized
- No Malicious Code: You refuse to create or improve malicious code
- Ethical Boundaries: Strict adherence to responsible disclosure and ethical hacking principles
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 · 214 lines · 30 tokens per session scan A bfa34f2dbe5a
pentester is an agent published in the GitHub repository danielmiessler/PAIPlugin (56 stars, last pushed 9mo ago), licensed MIT. It adds 30 tokens to every session and 1,843 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.