A command that combines reverse-engineering data into a detailed Markdown report. Reverse engineering means examining software or binaries to understand how they work.

Use it to create a dated report covering binaries, analysis progress, and findings in the project directory.

It turns findings, tracked analysis, session details, and existing reports into one organised record.

re-report — Command by ogrodev

Install

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.

agentmods

npx agentmods add commands/ogrodev/fsociety/re-report

Clone the repo

git clone --depth 1 https://github.com/ogrodev/fsociety

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. Scan, not verified.

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	$0.00006	$0.00456
Opus 5	$0.00003	$0.00228
Sonnet 5	$0.00001	$0.00091
Haiku 4.5	$0.00001	$0.00046

Measured 2d ago against content hash e8ffa6b52e31, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

re-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 2d 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.

romero/commands/re-report.md · 85 lines

What it actually says

Storage Policy: ALL output files MUST be saved in the project directory. NEVER write to /tmp/ or any system temporary directory.

Generate Analysis Report

This command compiles all analysis data into a comprehensive markdown report.

Step 1 — Gather Data

node "${CLAUDE_PLUGIN_ROOT}/scripts/analysis-tracker.js" list
node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list
node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list --db ioc
node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" show

Step 2 — Read Existing Reports

Check for existing analysis files in the project directory:

analysis-*.md
secrets-*.md
classify-*.md
diff-*.md
reports/*.md

Step 3 — Compile Report

Generate RE-REPORT-<date>.md with:

# Reverse Engineering Report

**Date:** <date>
**Analyst:** Romero RE Plugin
**Session:** <session-number>

## Executive Summary
<2-3 sentence overview of all analysis performed>

## Binary Inventory
| Binary | SHA256 | Type | Classification |
|--------|--------|------|----------------|

## Analysis Coverage
| Binary | Phase | Status | Findings |
|--------|-------|--------|----------|

## Findings by Severity

### CRITICAL
<findings>

### HIGH
<findings>

### MEDIUM
<findings>

### LOW / INFO
<findings>

## Indicators of Compromise (IOCs)
| Type | Value | Binary | Severity |
|------|-------|--------|----------|

## Technique Coverage
| Analysis Type | Count | Results |
|---------------|-------|---------|

## Risk Assessment
<overall risk evaluation based on findings>

## Recommendations
<actionable next steps>

Step 4 — Save

Save report to RE-REPORT-<date>.md in the project directory.

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.

2d ago First seen · 85 lines · 6 tokens per session scan A e8ffa6b52e31

Subscribe to this mod's changes

re-report is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 456 once invoked, about $0.0000 per session on Opus 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.

Security claude-code claude-code-plugin offensive-security pentesting

pr

Create a PR to main branch using conventional commit style for the title.

KeygraphHQ/shannon · 13 tokens

engage.scope

Execute Phase 0 - Scope Definition and Rules of Engagement.

hypnguyen1209/offensive-claude · 11 tokens

pentest

Activate pentest mode — displays ASCII art, configures session isolation, collects engagement scope, then OWNS the engagement: pre-flight, recon, planning (via the pentester-orchestrator planner), executor dispatch, a time-budget quota loop, aggregation, and report generation.

Stickman230/claude-pentest · 58 tokens

re-report