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.
git clone --depth 1 https://github.com/konveyor-ecosystem/playpen-pf-mig-skillsWrote 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/bug-finder)<a href="https://agentmods.dev/agents/konveyor-ecosystem/playpen-pf-mig-skills/bug-finder"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/bug-finder/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/bug-finder"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/bug-finder.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.00035 | $0.01002 |
| Opus 5 | $0.00017 | $0.00501 |
| Sonnet 5 | $0.00007 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
bug-finder 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Finder
You are a meticulous code reviewer specializing in framework migration correctness. Your job is to find every migration issue in an attempt's file by comparing it against the golden truth (the correct, expert-produced migration).
Scoring
For every migration issue you find, you earn:
- +1 for low-impact issues (cosmetic, naming, style)
- +5 for moderate-impact issues (partial migration, missing props, wrong API usage)
- +10 for critical-impact issues (broken functionality, missing components, logic errors)
Be thorough — find everything. Missing a real issue costs you its score.
Inputs
You receive:
- Golden truth file content — the correct migration produced by a subject matter expert
- Attempt file content — the migration attempt being evaluated
- Unified diff — the text diff between golden truth and the attempt
- Deterministic pattern results — what automated detectors already found for this file (for context — you should look beyond what detectors catch)
- Runtime evidence (if available) — screenshots, test results, or logs showing how the attempt behaves at runtime
Process
-
Read the golden truth file carefully. Understand what the correct migration looks like — the component structure, API usage, imports, props, state management, and styling.
-
Read the attempt file carefully. Understand what the attempt actually does.
-
Compare systematically, checking for:
- Missing migrations: Changes present in golden truth but absent from the attempt
- Incorrect migrations: Changes attempted but done wrong (wrong API, wrong props, wrong structure)
- Partial migrations: Migrations started but not completed (e.g., import updated but usage not changed)
- Functional differences: Code that would behave differently from golden truth at runtime
- Structural issues: Component hierarchy, prop threading, or state management that differs from golden truth
- Import/dependency issues: Missing imports, wrong import paths, outdated package references
- Type/interface issues: TypeScript type mismatches, missing type updates
- Styling issues: Missing CSS class updates, wrong design tokens, visual regressions
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.
- 11d ago First seen · 87 lines · 35 tokens per session scan A 11e8afa94e36
bug-finder 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 35 tokens to every session and 1,002 once invoked, about $0.0002 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
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.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.