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.
git clone --depth 1 https://github.com/ashrafmusa/agenticanaWrote 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/ashrafmusa/agenticana/penetration-tester)<a href="https://agentmods.dev/agents/ashrafmusa/agenticana/penetration-tester"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/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/ashrafmusa/agenticana/penetration-tester"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/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 | $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 9d 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.
- 9d ago First seen · 189 lines · 57 tokens per session scan A 383297115488
penetration-tester is an agent published in the GitHub repository ashrafmusa/agenticana (2 stars, last pushed 2d ago), licensed MIT. 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
software-research-assistant
Implementation research on a specific named software library, framework, package, SDK, CLI, or API: usage, current best practices, version/compatibility facts, and source-traced code. Use for "how do I implement X" or "which package for Y". Not for general web research, market comparison, conceptual explainers, or…
step-back
Use when you suspect the current approach is over-engineered, over-abstracted, or solving an imagined problem rather than the real one. Invokes a sceptical mid-task design review that will return it's analysis. Read-only - won't make changes.
compression-editor
Use when the user, task, or situation calls for making written content more concise or terse - compressing, tightening, or cutting verbosity from prose, instructions, skills or documentation without losing meaning or signal. Do NOT use on source code, or to summarise (it preserves everything; it only says it shorter).
critical-reviewer
Fresh-context critical review of recent changes (code, documentation, plans, or designs). Read-only. Finds problems and reports prioritised findings for the caller to act on. Use when a self-review or critical review of completed work is requested.
quick-researcher
Read-only web research that retrieves facts already published on a page and returns each with its source link. Two shapes: a single factual question ("what/which/when/how much/is X still..."), or a specified list of items to fill in - pricing tables, quotas, limits, version matrices - where every figure must come from…
azure-iac-exporter
Export existing Azure resources to Infrastructure as Code templates via Azure Resource Graph analysis, Azure Resource Manager API calls, and azure-iac-generator integration. Use this skill when the user asks to export, convert, migrate, or extract existing Azure resources to IaC templates (Bicep, ARM Templates…