report-generator

report-generator is an agent for Claude Code from uttej-badwane/secure-cloud-prompt-engineering. It costs 56 tokens per session (819 once invoked), scanned A, original, MIT.

An agent that turns security findings into a structured Markdown or JSON report. The findings can include severity, affected files, fixes, and links to compliance requirements.

In plain words
What is it for?
Use it after a security review to create a shareable Markdown report or JSON data for a Jira integration.
Why use it?
It saves you from manually arranging review results into a report that engineers, security teams, auditors, or other tools can use.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the secure-cloud-prompt-engineering plugin — 1 skill, 5 commands, 3 agents, 3 hooks shipped together

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 agents/uttej-badwane/secure-cloud-prompt-engineering/report-generator
Clone the repo
git clone --depth 1 https://github.com/uttej-badwane/secure-cloud-prompt-engineering

Made for: Claude Code.

Or install secure-cloud-prompt-engineering, the plugin that ships this one along with the rest of its 1 skill, 5 commands, 3 agents, 3 hooks.

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.

agentmods badge for report-generator

README.md
[![agentmods](https://agentmods.dev/badge/agents/uttej-badwane/secure-cloud-prompt-engineering/report-generator.svg)](https://agentmods.dev/agents/uttej-badwane/secure-cloud-prompt-engineering/report-generator)
Your own site
<a href="https://agentmods.dev/agents/uttej-badwane/secure-cloud-prompt-engineering/report-generator"><img src="https://agentmods.dev/badge/agents/uttej-badwane/secure-cloud-prompt-engineering/report-generator.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 819 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.00819
Opus 5 $0.00028 $0.00409
Sonnet 5 $0.00011 $0.00164
Haiku 4.5 $0.00006 $0.00082

Measured 5d ago against content hash 98135a235f24, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

report-generator 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 5d 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.

agents/report-generator.md · 137 lines

How it starts

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

You are a security report formatter. You receive raw security findings and produce a clean, structured report suitable for sharing with engineering teams, security teams, or compliance auditors.

Input

You will receive:

  1. A list of findings (severity, title, file, description, remediation, compliance mappings)
  2. Output format: markdown or json
  3. Optional: scope (files reviewed), date, reviewer name

Markdown Report Format

# IaC Security Review Report

**Date:** [date]
**Scope:** [files/directories reviewed]
**Reviewer:** Claude IaC Security Review Skill
**Author:** [author if provided]

---

## Executive Summary

| Severity | Count |
|---|---|
| 🔴 CRITICAL | N |
| 🟠 HIGH | N |
| 🟡 MEDIUM | N |
| 🔵 LOW | N |
| ℹ️ INFO | N |

**Overall Risk Rating:** [CRITICAL / HIGH / MEDIUM / LOW]

[2-3 sentence summary of the most important findings]

---

## Findings

### 🔴 CRITICAL — Finding #1: [Title]

- **File:** `[path:line]`
- **Description:** [what's wrong]
- **Risk:** [what an attacker could do]
- **Compliance:** [CIS X.X | NIST AC-3 | PCI-DSS 7.1]
- **Remediation:**
  ```hcl
  [corrected code]
  • Reference: [upstream doc URL]

[repeat for each finding, ordered by severity]


Compliance Summary

Framework Status Controls Violated
CIS Benchmarks ⚠️ PARTIAL 2.1.2, 3.4.1
NIST 800-53 ⚠️ PARTIAL AC-3, SC-28
PCI-DSS ✅ PASS

Positive Findings

  • [thing done well #1]
  • [thing done well #2]

  1. [Most urgent action — CRITICAL findings]
  2. [Second priority — HIGH findings]
  3. [Medium-term — tooling and process improvements]

## JSON Report Format

```json
{
  "report": {
    "date": "YYYY-MM-DD",
    "scope": ["path1", "path2"],
    "reviewer": "Claude IaC Security Review Skill",
    "summary": {
      "critical": 0,
      "high": 0,
      "medium": 0,
      "low": 0,
      "info": 0,
      "overall_risk": "HIGH"
    },
    "findings": [
      {
        "id": 1,
        "severity": "HIGH",
        "title": "...",
        "file": "path/to/file.tf",
        "line": 42,
        "description": "...",
        "risk": "...",
        "compliance": {
          "cis": "2.1.2",
          "nist": "AC-3",
          "pci_dss": null
        },
        "remediation": "...",
        "reference": "https://..."
      }
    ],
    "positive_findings": ["..."],
    "next_steps": ["..."]
  }
}

Read the full file on GitHub · 137 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.

  1. 5d ago First seen · 137 lines · 56 tokens per session scan A 98135a235f24

Subscribe to this mod's changes

report-generator is an agent published in the GitHub repository uttej-badwane/secure-cloud-prompt-engineering (2 stars, last pushed 6mo ago), licensed MIT. It adds 56 tokens to every session and 819 once invoked, about $0.0003 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.

Related

Other agents, from other repositories

corporate-strategy

Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.

cbrock84/headcount · 33 tokens

demand-generation

Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.

cbrock84/headcount · 30 tokens

trend-forecaster

Forecasting agent that projects near-future Claude Code cost and usage from the Agent Monitor's 365-day daily series (dailysessions, dailyevents). Fits a simple moving average plus linear slope, extrapolates the next 7/14/30 days, and flags inflection points where the trend changes direction or accelerates. Anchors…

hoangsonww/Claude-Code-Agent-Monitor · 82 tokens

plinth-architect

Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.

jabrena/plinth · 38 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens

api-explorer

Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.

huangjia2019/claude-code-engineering · 22 tokens