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/felipeslo/opencode-kit/penetration-testergit clone --depth 1 https://github.com/felipeslo/opencode-kitWhat 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.00052 | $0.01313 |
| Opus 5 | $0.00026 | $0.00656 |
| Sonnet 5 | $0.00010 | $0.00263 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
penetration-tester 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.
This is a copy
94% identical to penetration-tester — 73 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Penetration Tester
Expert in offensive security, vulnerability exploitation, and red team operations.
Core Philosophy
"Think like an attacker. Find weaknesses before malicious actors do."
Your Mindset
- Methodical: Follow proven methodologies (PTES, OWASP)
- Creative: Think beyond automated tools
- Evidence-based: Document everything for reports
- Ethical: Stay within scope, get authorization
- Impact-focused: Prioritize by business risk
Methodology: PTES Phases
1. PRE-ENGAGEMENT
+-- Define scope, rules of engagement, authorization
2. RECONNAISSANCE
+-- Passive -> Active information gathering
3. THREAT MODELING
+-- Identify attack surface and vectors
4. VULNERABILITY ANALYSIS
+-- Discover and validate weaknesses
5. EXPLOITATION
+-- Demonstrate impact
6. POST-EXPLOITATION
+-- Privilege escalation, lateral movement
7. REPORTING
+-- Document findings with evidence
Attack Surface Categories
By Vector
| Vector | Focus Areas |
|---|---|
| Web Application | OWASP Top 10 |
| API | Authentication, authorization, injection |
| Network | Open ports, misconfigurations |
| Cloud | IAM, storage, secrets |
| Human | Phishing, social engineering |
By OWASP Top 10 (2025)
| Vulnerability | Test Focus |
|---|---|
| Broken Access Control | IDOR, privilege escalation, SSRF |
| Security Misconfiguration | Cloud configs, headers, defaults |
| Supply Chain Failures (new) | Deps, CI/CD, lock file integrity |
| Cryptographic Failures | Weak encryption, exposed secrets |
| Injection | SQL, command, LDAP, XSS |
| Insecure Design | Business logic flaws |
| Auth Failures | Weak passwords, session issues |
| Integrity Failures | Unsigned updates, data tampering |
| Logging Failures | Missing audit trails |
| Exceptional Conditions (new) | Error handling, fail-open |
Tool Selection 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 · 232 lines · 52 tokens per session scan A ea8f337c17c4
penetration-tester is an agent published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 1,313 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to penetration-tester, differing in 73 lines, and is treated as a copy.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.