A reporting workflow that turns penetration-test notes, evidence, and case files into structured security findings and an interactive dashboard. A penetration test is an authorized check for weaknesses in systems.

Use it to turn Markdown reports or finding files into machine-readable results and render them in a security dashboard.

It removes the need to keep findings only in loosely formatted reports. Structured findings make severity, identifiers, and dashboard data easier to keep consistent.

reporting — Skill for Claude Code and Codex by xAmirHamza77

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/xAmirHamza77/ReverseOps-Skill

agentmods

npx agentmods add skills/xamirhamza77/reverseops-skill/reporting

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/reporting/github.svg)](https://agentmods.dev/skills/xamirhamza77/reverseops-skill/reporting)

Your own site

<a href="https://agentmods.dev/skills/xamirhamza77/reverseops-skill/reporting"><img src="https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/xamirhamza77/reverseops-skill/reporting"><img src="https://agentmods.dev/badge/skills/xamirhamza77/reverseops-skill/reporting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 798 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00798
Opus 5	$0.00000	$0.00399
Sonnet 5	$0.00000	$0.00160
Haiku 4.5	$0.00000	$0.00080

Measured 6d ago against content hash a9b0043bcb5c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

reporting 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 6d 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.

skills/reporting/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

reporting — findings schema, panel export, report automation

Purpose: turn raw engagement output (reports/*.md, evidence chains, case dirs) into machine-readable findings and an interactive dashboard — the ReverseOps panel (panel/).

When this skill fires

"write up the findings", "generate the report", "make a dashboard", "pentest report"
After any ACT phase completes (Evidence → Finding → Path lands, then this skill renders it)
When the user opens panel/index.html and it shows stale / no data

Contract

Every finding is data first. Either:
- a JSON file conforming to skills/reporting/finding-schema.json (work/<case>/findings/HIG-001.json, one file per finding), or
- a ## Finding N: title (or ## vulnerability N：标题) section inside a markdown report with an inline Severity: / risk等级： line — the exporter parses these heuristically.
Severity vocabulary is fixed: critical | high | medium | low | info (Chinese reports' critical / high risk / medium risk / low risk / info map onto these automatically).
IDs are stable: <SEV3>-<NNN> (HIG-001). Never renumber a finding that a client has seen.

Workflow

evidence chain (skills/ops/evidence-finding-path.md)
  → write finding JSON (work/<case>/findings/*.json)        # preferred
    OR structured section in reports/<date>_<case>.md
  → python3 scripts/mkreport.py                             # repo-local defaults
  → python3 panel/serve.py  → http://127.0.0.1:8377          # dashboard + terminal

mkreport.py outputs panel/data/data.js + panel/data/data.json. Both are gitignored — regeneration is a local step, never commit client data.
Extra sources: --findings-dir <dir>, --include <file>, --cases-root work.
Panel from file://? It falls back to bundled panel/data/sample.data.js when data.js is missing, tagged DEMO in the header. Terminal + report-body view need serve.py.

ACTION REQUIRED

Confirm each finding has ≥1 evidence ref (evidence[]) before setting status: confirmed — mirrors skills/ops/scope-contract.md (no evidence, no finding).
Run python3 scripts/mkreport.py and read the warning list; fix unparsed sections.
Open the panel, verify severity counts match the markdown report by hand once.
Redact before sharing: grep -Ri 'token\|password\|secret' panel/data/ then delete the export.

Read the full file on GitHub · 63 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

6d ago First seen · 63 lines · 0 tokens per session scan A a9b0043bcb5c

Subscribe to this mod's changes

reporting is a skill published in the GitHub repository xAmirHamza77/ReverseOps-Skill (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 798 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-09-03.

Analytics and metrics Security ai claude claude-skills mcp-server mcp-tools penetration-testing

building-mcp-servers

Use this skill whenever the user wants to design, build, harden, review, or debug an MCP (Model Context Protocol) server — including "build me an MCP server for X", connecting an AI agent/Claude to a database or API, adding tools/resources to an existing MCP server, reviewing a contributor PR against an MCP server, or…

cyberreinxy/mcp-server-skill · 160 tokens

scanner-pmcc

Scan stocks for Poor Man's Covered Call (PMCC) suitability. Analyzes LEAPS and short call options for delta, liquidity, spread, IV, yield, trend direction, and earnings proximity. Use when user asks about PMCC candidates, diagonal spreads, or LEAPS strategies.

staskh/trading_skills · 63 tokens

ib-collar

Generate tactical collar strategy reports for protecting PMCC positions through earnings or high-risk events. Requires TWS or IB Gateway running locally.

staskh/trading_skills · 30 tokens

ib-portfolio-action-report

Generate a comprehensive portfolio action report with earnings dates and risk assessment. Use when user asks for portfolio review, action items, earnings risk, or position management across IB accounts. Requires TWS or IB Gateway running locally.

staskh/trading_skills · 49 tokens

ib-trades-history

Fetch trade executions from Interactive Brokers filtered by account, date range, or symbol. Supports live API (7 days history) and FlexReport (full history). Use when user asks about their trades, executions, or transaction history. Requires TWS or IB Gateway running locally.

staskh/trading_skills · 59 tokens

report-stock

Generate comprehensive stock analysis report (PDF or markdown) with trend, PMCC, and fundamental analysis.

staskh/trading_skills · 22 tokens