opencode-kit: Agent for Claude Code

.opencode/agents/penetration-tester.md

penetration-tester is an agent for Claude Code, OpenCode from felipeslo/opencode-kit. It costs 52 tokens per session (1,313 once invoked), scanned A, a copy of penetration-tester, MIT.

An assistant for authorized security testing that looks for ways attackers could exploit weaknesses in websites, APIs, networks, and cloud systems.

In plain words
What is it for?
Use it to plan penetration tests, assess vulnerabilities, simulate attacks, check their impact, and prepare evidence-based reports.
Why use it?
It helps find and document security problems before malicious attackers discover them.

Agent for Claude CodeOpenCode

Written for OpenCode and Claude Code: installed under .opencode/, but also a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

This is felipeslo/opencode-kit's own configuration. It tells Claude Code and OpenCode how to work on opencode-kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything opencode-kit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to felipeslo/opencode-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/felipeslo/opencode-kit/main/.opencode/agents/penetration-tester.md
Clone the repo
git clone --depth 1 https://github.com/felipeslo/opencode-kit

Made for: Claude Code, OpenCode.

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.

agentmods badge for penetration-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/felipeslo/opencode-kit/penetration-tester/github.svg)](https://agentmods.dev/agents/felipeslo/opencode-kit/penetration-tester)
Your own site
<a href="https://agentmods.dev/agents/felipeslo/opencode-kit/penetration-tester"><img src="https://agentmods.dev/badge/agents/felipeslo/opencode-kit/penetration-tester/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.

agentmods 80×15 button for penetration-tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/felipeslo/opencode-kit/penetration-tester"><img src="https://agentmods.dev/badge/agents/felipeslo/opencode-kit/penetration-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,313 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 94% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.01313
Opus 5.5 $0.00021 $0.00525
Sonnet 5.5 $0.00010 $0.00263
Haiku 4.5 $0.00005 $0.00131

Measured 1mo ago against content hash ea8f337c17c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

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.

.opencode/agents/penetration-tester.md · 232 lines

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

Read the full file on GitHub · 232 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.

  1. 1mo ago First seen · 232 lines · 52 tokens per session scan A ea8f337c17c4

Subscribe to this mod's changes

penetration-tester is an agent published in the GitHub repository felipeslo/opencode-kit (2 stars, last pushed 7mo ago), licensed MIT. It adds 52 tokens to every session and 1,313 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other agents, from other repositories