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.
git clone --depth 1 https://github.com/konveyor-ecosystem/playpen-pf-mig-skillsnpx agentmods add agents/konveyor-ecosystem/playpen-pf-mig-skills/comparison-report-generatorWrote 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/konveyor-ecosystem/playpen-pf-mig-skills/comparison-report-generator)<a href="https://agentmods.dev/agents/konveyor-ecosystem/playpen-pf-mig-skills/comparison-report-generator"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/comparison-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.
<a href="https://agentmods.dev/agents/konveyor-ecosystem/playpen-pf-mig-skills/comparison-report-generator"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/comparison-report-generator.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00544 |
| Opus 5 | $0.00010 | $0.00272 |
| Sonnet 5 | $0.00004 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
comparison-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 12d 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.
What it actually says
Comparison Report Generator
Enrich comparison data with migration-context annotations and generate the final HTML report.
Inputs
- Workspace directory: path containing
comparison-data.json - Label A: human-readable label for reference A
- Label B: human-readable label for reference B
Process
1. Read Comparison Data
Read <workspace>/comparison-data.json. Understand the overall shape:
- How many files were modified, added, removed
- What change categories are present
- What errors occurred (if any)
2. Annotate Significant Changes
For the top ~20 most significant changes (prioritize by: api_changes first, then semantic, then structural, then additive/subtractive — skip cosmetic), do the following:
- Read the source files from both directories (paths are in
metadata.repo_a.pathandmetadata.repo_b.path) - Read the
text_difffor the file fromcomparison-data.json - Write a concise natural-language annotation (1-3 sentences) describing what changed in migration context. Focus on:
- What API was changed and why it matters
- What behavior changed
- Whether the change looks intentional or accidental
- How it compares between the two references
Add each annotation to the annotations array in comparison-data.json:
{
"path": "src/App.tsx",
"text": "Changed PageSection variant from 'light' to 'default' — this is the PF6 equivalent of the deprecated 'light' variant."
}
3. Write Updated Data
Write the updated comparison-data.json with the annotations added.
4. Generate HTML Report
Run:
python3 scripts/generate_comparison_report.py <workspace>
This produces <workspace>/comparison-report.html.
5. Verify Report
Confirm that comparison-report.html exists and is non-empty.
Output
Return the path to comparison-report.html:
Report generated: <workspace>/comparison-report.html
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.
- 12d ago First seen · 80 lines · 19 tokens per session scan A da9cc634c159
comparison-report-generator is an agent published in the GitHub repository konveyor-ecosystem/playpen-pf-mig-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 544 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.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.