A command that turns the latest security audit into a shareable report. An audit is a review that looks for problems in code, and the report can be produced as Markdown, HTML, PDF, JSON, or an image.

Use it after running an audit to create an executive summary, findings list, methodology, remediation details, and other audit deliverables.

It saves you from assembling audit findings, severity counts, evidence, fixes, and limitations into a report by hand.

report — Command for coding agents by omermaksutii: A command that turns the latest security audit into…

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/omermaksutii/rugproof/report

Clone the repo

git clone --depth 1 https://github.com/omermaksutii/RugProof

Or install rugproof, the plugin that ships this one along with the rest of its 35 commands, 23 agents.

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

When invoked 725 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.00020	$0.00725
Opus 5	$0.00010	$0.00362
Sonnet 5	$0.00004	$0.00145
Haiku 4.5	$0.00002	$0.00072

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

Security

Grade A, and why

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 3d 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.

commands/report.md · 65 lines

How it starts

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

/report — generate audit deliverable

Take the most recent /audit (or /audit-deep) result and render it as a deliverable. Default formats from .rugproof.yml report.formats.

Procedure

Step 1 — Locate findings

If a recent audit isn't in conversation context, ask the user to run /audit first, or point them at rugproof-reports/findings.json if it exists.

Step 2 — Build the report sections

Executive summary — 4-6 sentences. Lead with the dollar value at risk, the number of Critical findings, and the trust level. Suitable for executives.
Severity overview — counts table, grade.
Trust report (centralization findings) — from [[centralization-risk]] format.
Findings — one section per finding, sorted by severity descending:
- Title, ID, severity, confidence
- File path:line + code block of the offending lines
- Description (what / how / why)
- Impact + likelihood
- Remediation patch (diff)
- Historical context if any
Methodology — which skills ran, which specialist subagents dispatched, scope (lines audited).
Out of scope / known limitations — be honest about what wasn't checked.
Appendix — tool versions, MCP server versions, git commit, contract addresses.

Step 3 — Dispatch report-writer subagent

For long reports, dispatch the report-writer subagent with the raw findings — it will produce polished prose without consuming the main context.

Step 4 — Render formats

For each requested format, use the corresponding template in templates/:

markdown → templates/report.md.hbs → rugproof-reports/audit-YYYY-MM-DD.md
html → templates/report.html.hbs → styled, navigable, collapsible sections
pdf → render HTML through headless Chrome / wkhtmltopdf
json → structured findings + metadata for CI / dashboards
png → templates/audit-card.svg.hbs → run through resvg or sharp (use /card internally)

Step 5 — Output

Tell the user where the files are:

Read the full file on GitHub · 65 lines

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.

3d ago First seen · 65 lines · 20 tokens per session scan A 5fe515538de2

Subscribe to this mod's changes

report is a command published in the GitHub repository omermaksutii/RugProof (9 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 725 once invoked, about $0.0001 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-31.

Documents PDF Security berachain blockchain claude-code claude-code-plugin defi ethereum

report

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/report — generate audit deliverable

Procedure

Step 1 — Locate findings

Step 2 — Build the report sections

Step 3 — Dispatch report-writer subagent

Step 4 — Render formats

Step 5 — Output

What this file has done since we first saw it

Other commands, from other repositories

phase6-start

codespace-verify

pr-merge

compile_paper

latex-posters

open