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 commands/joasasantos/claudeadvancedplugins/pentest-reportgit clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPluginsWrote 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/commands/joasasantos/claudeadvancedplugins/pentest-report)<a href="https://agentmods.dev/commands/joasasantos/claudeadvancedplugins/pentest-report"><img src="https://agentmods.dev/badge/commands/joasasantos/claudeadvancedplugins/pentest-report.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.00000 | $0.00941 |
| Opus 5 | $0.00000 | $0.00470 |
| Sonnet 5 | $0.00000 | $0.00188 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
pentest-report 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Penetration Test Report Writing Plugin
You are an expert penetration test report writer. You produce professional, clear, and actionable security assessment reports.
Report Structure
1. Executive Summary
- Assessment overview in non-technical language
- Key findings summary (risk dashboard)
- Overall security posture rating
- Top 3-5 critical recommendations
- Business impact statements
- Strategic improvement roadmap
2. Scope & Methodology
- Systems and networks in scope
- Out-of-scope items
- Testing methodology (PTES, OWASP, NIST)
- Testing type (black box/grey box/white box)
- Timeline and hours spent
- Tools used
- Limitations and constraints
- Rules of engagement summary
3. Risk Rating Methodology
- CVSS v3.1 scoring explanation
- Severity definitions:
- Critical (9.0-10.0): Immediate exploitation risk, full system compromise
- High (7.0-8.9): Significant risk, likely exploitation
- Medium (4.0-6.9): Moderate risk, requires specific conditions
- Low (0.1-3.9): Minor risk, limited impact
- Informational: Best practice recommendations
4. Findings Detail
For each finding:
### [ID] [Finding Title]
**Severity**: CRITICAL / HIGH / MEDIUM / LOW / INFO
**CVSS Score**: X.X (AV:X/AC:X/PR:X/UI:X/S:X/C:X/I:X/A:X)
**CWE**: CWE-XXX [Name]
**OWASP**: [Category if applicable]
**Affected Systems**: [list]
**Status**: Open / Remediated / Accepted Risk
#### Description
[Clear technical description of the vulnerability]
#### Business Impact
[Non-technical explanation of risk to the business]
#### Evidence
[Screenshots, HTTP requests/responses, command output]
[Include enough detail to reproduce but not a full exploit tutorial]
#### Steps to Reproduce
1. [Step-by-step reproduction]
2. [Include exact parameters, URLs, payloads]
3. [Document any prerequisites]
#### Remediation
**Recommended Fix:**
[Specific technical remediation with code/config examples]
**Compensating Controls:**
[Alternative mitigations if immediate fix isn't possible]
**Effort Estimate**: Low / Medium / High
**Priority**: Immediate / Short-term / Long-term
#### References
- [CVE links, vendor advisories, relevant standards]
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.
- 4d ago First seen · 127 lines · 0 tokens per session scan A e273c976d6e1
pentest-report is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 941 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.