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 skills add s0ld13rr/pentestcode --skill reportinggit clone --depth 1 https://github.com/s0ld13rr/pentestcodeWrote 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/skills/s0ld13rr/pentestcode/reporting)<a href="https://agentmods.dev/skills/s0ld13rr/pentestcode/reporting"><img src="https://agentmods.dev/badge/skills/s0ld13rr/pentestcode/reporting/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/skills/s0ld13rr/pentestcode/reporting"><img src="https://agentmods.dev/badge/skills/s0ld13rr/pentestcode/reporting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00579 |
| Opus 5.5 | $0.00010 | $0.00232 |
| Sonnet 5.5 | $0.00005 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
reporting-phase 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Generation Guide
Finding Format
Each finding should include:
### [SEVERITY] Finding Title
- **Target**: IP:port or URL
- **CVSS/Severity**: Critical/High/Medium/Low/Info
- **CVE**: CVE-XXXX-XXXXX (if applicable)
- **ATT&CK**: TXXXX (technique ID)
- **Status**: Confirmed / Exploited
**Description**: What the vulnerability is and why it matters.
**Evidence**: Command run + output proving the vulnerability.
**Impact**: What an attacker can achieve by exploiting this.
**Remediation**: Specific steps to fix the issue.
Report Structure
Executive Summary
- Engagement scope and dates
- Overall risk rating (Critical/High/Medium/Low)
- Key findings count by severity
- Top 3 most critical issues
- Strategic recommendations (2-3 sentences)
Methodology
- Phases performed
- Tools used
- Scope boundaries
Findings (grouped by severity)
- Critical findings
- High findings
- Medium findings
- Low findings
- Informational
Attack Path Narrative
Step-by-step description of successful attack chains:
- Initial access vector
- Privilege escalation path
- Lateral movement
- Data accessed
Host Summary Table
| Host | OS | Services | Vulns | Access |
|---|
Recommendations
Prioritized remediation list:
- Immediate (Critical/High) — fix within 48h
- Short-term (Medium) — fix within 30 days
- Long-term (Low/Info) — fix within 90 days
Severity Classification
- Critical (CVSS 9.0-10.0): RCE, auth bypass, default creds on critical systems, full DB dump
- High (CVSS 7.0-8.9): Arbitrary file read/write, privesc, SSRF to internal, stored XSS on admin
- Medium (CVSS 4.0-6.9): Reflected XSS, sensitive info disclosure, missing security headers with impact
- Low (CVSS 0.1-3.9): Version disclosure, minor info leaks, missing non-critical headers
- Info (CVSS 0.0): Open ports, technology detection, informational findings
Output Formats
Use the report_gen tool to generate:
- Markdown report (default)
- JSON export (machine-readable)
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 · 78 lines · 24 tokens per session scan A 5c9729250edb
reporting-phase is a skill published in the GitHub repository s0ld13rr/pentestcode (851 stars, last pushed 15d ago), licensed MIT. It adds 24 tokens to every session and 579 once invoked, about $0.0001 per session on Opus 5.5. 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 skills, from other repositories
lictor-security-check
Pre-release security audit for ANY project — AI-built or hand-written, web or mobile. Scans the codebase for the full range of real-world risks that get apps breached: leaked API & AI-provider keys, exposed configs/secrets, broken auth & access control (IDOR), injection (SQL/XSS/command), SSRF, open databases & cloud…
lictor-rotate
Walks the user through rotating a leaked API key — step by step, provider-specific. Knows the exact URL to visit, the exact button to click, and how to verify the rotation worked. Supports Stripe, OpenAI, Anthropic, Google Cloud / AI Studio, GitHub, AWS, Slack, Supabase, Firebase, Postmark, and generic OAuth providers.
lictor-explain
Takes any security finding, error message, or jargon-heavy security advice and explains it in plain English. Use this when someone is confused by what /lictor-security-check found, or when they got a security warning from another tool and don't understand it.
finance-analysis-analyst
Drive repeatable finance variance analysis with clear assumptions, reconciliations, and executive summaries.
openai-patterns
Production OpenAI API patterns — model selection, prompt engineering, function calling, streaming, error handling, cost control, and structured outputs.
notion-weekly-report
Produce weekly progress summaries from Notion sources.