report-generator

report-generator is an agent for Claude Code from konveyor-ecosystem/playpen-pf-mig-skills. It costs 34 tokens per session (1,656 once invoked), scanned A, original, Apache-2.0.

An agent that builds a migration report from workspace files such as status notes, screenshots, visual reports, and assessment results. A migration report summarizes progress when moving a project from one technology or version to another.

In plain words
What is it for?
Use it to read migration status, inspect screenshots and Kantra results, create report-data.json, and generate an HTML report.
Why use it?
It gathers scattered migration evidence into one structured report and highlights completed work, remaining issues, and items needing human review.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions Claude Code; mentions Gemini CLI.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/generate_migration_report.py <work_dir>.

Good fit Use it to read migration status, inspect screenshots and Kantra results, create report-data.json, and generate an HTML report.

Compare 6 agents from other repositories ↓
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/konveyor-ecosystem/playpen-pf-mig-skills
agentmods
npx agentmods add agents/konveyor-ecosystem/playpen-pf-mig-skills/report-generator

Made for: Claude Code.

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/konveyor-ecosystem/playpen-pf-mig-skills/report-generator/github.svg)](https://agentmods.dev/agents/konveyor-ecosystem/playpen-pf-mig-skills/report-generator)
Your own site
<a href="https://agentmods.dev/agents/konveyor-ecosystem/playpen-pf-mig-skills/report-generator"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/report-generator/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.

agentmods 80×15 button for report-generator

Your own site · 80×15
<a href="https://agentmods.dev/agents/konveyor-ecosystem/playpen-pf-mig-skills/report-generator"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/report-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,656 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01656
Opus 5.5 $0.00014 $0.00662
Sonnet 5.5 $0.00007 $0.00331
Haiku 4.5 $0.00003 $0.00166

Measured 2mo ago against content hash f6067e88a912, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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 · 178 lines

How it starts

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

Report Generator

Generate a migration report by reading workspace artifacts, building report-data.json, and producing an HTML report.

Inputs

  • Work directory: workspace root (contains status.md, screenshot directories, visual reports)
  • Source technology: the migration source (e.g., "PatternFly 5")
  • Target technology: the migration target (e.g., "PatternFly 6")
  • Project path: path to the project being migrated

Process

1. Read status.md

Read <work_dir>/status.md and extract:

  • Complete section: total rounds, build/test/validation status
  • Groups: list of groups with their completion status
  • Group Details: for each group — name, description, files, issues
  • Round Log: each round's fixed count, new issues, build/test results
  • Action Required section: items the user must review (unresolved issues, false positives, visual reviews, manual interventions)

2. Read Kantra Assessment

Check for the latest Kantra output directory (<work_dir>/round-*/kantra/output.yaml). If a final round exists, note any residual incidents (rule, count, reason for keeping).

If no Kantra output exists, set kantra_residual.total_incidents to 0.

3. Read Visual Comparison Report

If <work_dir>/visual-diff-report.md exists, extract per-page results (page name, status, notes). Map unchecked items ([ ]) to fail status and checked items ([x]) to pass.

4. List Screenshot Directories

Check for <work_dir>/baseline/ and <work_dir>/post-migration/ directories. List filenames in each to populate the visual pages array.

If neither directory exists, set visual.has_screenshots to false.

5. Build report-data.json

Create <work_dir>/report-data.json using the following schema:

{
  "migration": {
    "source": "string",
    "target": "string",
    "project": "string (project path)",
    "timestamp": "ISO 8601",
    "workspace": "string (workspace path)"
  },
  "summary": {
    "total_rounds": "number",
    "status": "complete|incomplete",
    "build": "PASS|FAIL",
    "unit_tests": "PASS|FAIL|NONE",
    "e2e_tests": "PASS|FAIL|NONE",
    "lint": "PASS|FAIL|NONE",
    "target_validation": "PASS|FAIL|NONE"
  },
  "action_required": [
    {
      "type": "unresolved_issue|false_positive|visual_review|manual_intervention",
      "description": "string",
      "recommendation": "string (optional)",
      "details": "string (optional)",
      "page": "string (optional, for visual_review)"
    }
  ],
  "groups": [
    {
      "name": "string",
      "status": "complete|incomplete",
      "issues_fixed": "number",
      "files": ["string"],
      "description": "string"
    }
  ],
  "rounds": [
    {
      "number": "number",
      "group": "string",
      "issues_fixed": "number",
      "new_issues": "number",
      "build": "PASS|FAIL",
      "tests": "string (e.g. '265/265' or '225/262 (37 snapshot mismatches)')"
    }
  ],
  "visual": {
    "has_screenshots": "boolean",
    "baseline_dir": "string (relative to work_dir)",
    "post_migration_dir": "string (relative to work_dir)",
    "pages": [
      {
        "name": "string",
        "baseline": "string (filename, e.g. 'login.png')",
        "post_migration": "string (filename, e.g. 'login.png')",
        "status": "pass|fail|info",
        "notes": "string"
      }
    ]
  },
  "kantra_residual": {
    "total_incidents": "number",
    "categories": [
      {
        "rule": "string",
        "count": "number",
        "reason": "string"
      }
    ]
  }
}

Read the full file on GitHub · 178 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. 2mo ago First seen · 178 lines · 34 tokens per session scan A f6067e88a912

Subscribe to this mod's changes

report-generator is an agent published in the GitHub repository konveyor-ecosystem/playpen-pf-mig-skills (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,656 once invoked, about $0.0001 per session on Opus 5.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

report-generator compared with agents from other repositories

report-generator next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
report-generatorkonveyor-ecosystem/playpen-pf-mig-skillsAgent26mo agoApache-2.0A34Claude Code
quarto-criticbrycewang-stanford/Auto-Empirical-Research-SkillsAgent5.0k5d agononeA38Claude Code
openwriter-enrichment-miniontravsteward/openwriterAgent366d agoMITA19Claude Code
report-generatordaemon-blockint-tech/GrondAgent21mo agoMITA195Claude Code
chronology-builderfedec65/bettercallclaudeAgent461mo agoAGPL-3.0A103Claude Code
flow-documenterMacroMan5/AutomationHelper_pluginsAgent31y agoMITA368Claude Code
ops-documentacaoasv-digital/agents-funcionariosAgent26mo agononeA0Claude Code