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 agentmods add agents/uttej-badwane/secure-cloud-prompt-engineering/report-generatorgit clone --depth 1 https://github.com/uttej-badwane/secure-cloud-prompt-engineeringWrote 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/agents/uttej-badwane/secure-cloud-prompt-engineering/report-generator)<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>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.00056 | $0.00819 |
| Opus 5 | $0.00028 | $0.00409 |
| Sonnet 5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
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.
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:
- A list of findings (severity, title, file, description, remediation, compliance mappings)
- Output format:
markdownorjson - 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]
Recommended Next Steps
- [Most urgent action — CRITICAL findings]
- [Second priority — HIGH findings]
- [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": ["..."]
}
}
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.
- 5d ago First seen · 137 lines · 56 tokens per session scan A 98135a235f24
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.
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.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
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…
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.
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…
api-explorer
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.