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/diillson/chatcli/penetration-testergit 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.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.01088 |
| Opus 5 | $0.00028 | $0.00544 |
| Sonnet 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 3d 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.
- 3d ago First seen · 189 lines · 57 tokens per session scan A 383297115488
penetration-tester is an agent published in the GitHub repository diillson/chatcli (89 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 1,088 once invoked, about $0.0003 per session on Opus 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
story-explorer
故事项目结构化查询 agent（只读）。响应关于角色状态、伏笔进度、设定出现位置、 时间线节点、写作进度的查询。使用 grep + read 从项目文件系统中检索信息， 返回结构化 JSON 摘要。 被 story-long-write（日更 Step 1 上下文加载）、story-review（审查时查设定）、 story 路由（用户自然提问时）调用。 不做任何创作判断或修改。.
story-architect
故事架构与世界观创作专家。负责题材选择、核心梗设计、世界观构建、大纲排布、 钩子/悬念/反转等叙事工程、情绪弧线设计、范围控制审查。 被 story-long-write（Phase 1-3）、story-short-write（Phase 1-2）调用。 也可审查已有内容的结构问题。.
work-verifier
Validates completed work. Use after tasks are marked done to confirm implementations are functional.
debugger
Debugging specialist for errors and test failures. Use when encountering issues.
test-runner
Test automation expert. Use proactively to run tests and fix failures.
design-reviewer
你是设计评审员。以独立第三方视角审查架构设计，关注设计健全性、与领域模型的一致性、以及是否存在过早优化或遗漏。你不修改设计文档，只输出发现。.