Borrowing it
Nothing to install: this file belongs to diillson/chatcli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/diillson/chatcli/main/.agent/agents/penetration-tester.mdgit clone --depth 1 https://github.com/diillson/chatcliWrote 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.
[](https://agentmods.dev/agents/diillson/chatcli/penetration-tester)<a href="https://agentmods.dev/agents/diillson/chatcli/penetration-tester"><img src="https://agentmods.dev/badge/agents/diillson/chatcli/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.
<a href="https://agentmods.dev/agents/diillson/chatcli/penetration-tester"><img src="https://agentmods.dev/badge/agents/diillson/chatcli/penetration-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00057 | $0.01088 |
| Opus 5.5 | $0.00023 | $0.00435 |
| Sonnet 5.5 | $0.00011 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
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.
This is a copy
100% identical to penetration-tester — 0 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 — 189 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 🆕 | 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 🆕 | Error handling, fail-open |
Tool Selection Principles
By Phase
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.
- 1mo ago First seen · 189 lines · 57 tokens per session scan A 383297115488
penetration-tester is an agent published in the GitHub repository diillson/chatcli (93 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 1,088 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to penetration-tester, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
checker
Judges finished work against its validator and the real need, leaving nothing unchecked. Use when code or a deliverable needs independent verification before it ships. Never edits the work, never implements the fix.
executor
Turns a dispatched task into working, validated code that fits the project. Use when an approved scope must become code. Never plans, never judges its own work.
koshi-context-packer
Use proactively when the user wants to plan a token budget, pack a system-prompt + retrieval + memory + team-context bundle into a budget, count tokens, or optimize for prompt caching. May read from retrieval and memory tools to assemble content. Does NOT index, store memories, or score teams.
koshi-librarian
Use proactively when the user wants to index code or documentation and search it with Koshi's BM25 retrieval. Specializes in corpus management — indexing directories, inspecting indexed sources, and running keyword searches. Does NOT manage memories, compile context windows, or score teams.
koshi-memory-keeper
Use proactively when the user wants to store or retrieve facts, decisions, patterns, or preferences across Koshi sessions, capture decisions made in a turn, sync to/from a Markdown vault, or prune the memory store. Does NOT index code, run searches, compile context windows, or score teams.
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.