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/visual-fix)<a href="https://agentmods.dev/agents/konveyor-ecosystem/playpen-pf-mig-skills/visual-fix"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/visual-fix/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/visual-fix"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/visual-fix.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.00023 | $0.01520 |
| Opus 5 | $0.00012 | $0.00760 |
| Sonnet 5 | $0.00005 | $0.00304 |
| Haiku 4.5 | $0.00002 | $0.00152 |
Grade A, and why
visual-fix scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf -o /dev/null <dev_url> 2>/dev/null && echo "READY" || echo "NOT_READY" How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Fix
Fix unchecked visual issues from visual-diff-report.md.
Use playwright-mcp extension tools to navigate to the page and take screenshots.
Assume user confirmation for all actions. Do not prompt for user input.
Inputs
- Work directory: contains
baseline/,manifest.md, andvisual-diff-report.md - Post-migration directory: the current post-migration screenshot directory (e.g.,
<work_dir>/post-migration) - Project path: path to the project source code
- Migration context: brief 2-3 line summary of the ongoing migration — what technologies are involved and what has been done so far
- Dev URL: the dev server URL, already verified as responsive by the main agent (e.g.,
http://localhost:9000)
Ground Rules
- Baseline is the source of truth. Make post-migration match baseline exactly. Do not rationalize differences.
- Compare regions independently. Masthead, sidebar, content area, modals may each have different styling.
- Verify fixes against baseline, not your expectations. Take a screenshot and compare it to baseline.
- Do not create CSS override files (e.g.,
pf6-overrides.css). Fix the root cause in component code. - Do not write PIL/pixel analysis scripts. Use
playwright-mcpto take screenshots and visually inspect them.
Process
1. Understand Context
Read <work_dir>/status.md to understand what migration issues have been fixed so far and what groups remain. This helps identify root causes of visual regressions.
2. Read Report
Read <work_dir>/visual-diff-report.md. Collect all unchecked ([ ]) issues.
If no unchecked issues exist, report success and stop.
3. Verify Dev Server
The main agent has already started the dev server. Confirm it is responsive:
curl -sf -o /dev/null <dev_url> 2>/dev/null && echo "READY" || echo "NOT_READY"
If NOT_READY, report the error and stop. Do not attempt to start the dev server yourself — never run npm start, npx webpack serve, or any other startup command. The main agent is responsible for server lifecycle.
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 · 134 lines · 23 tokens per session scan A 4bf380f29258
visual-fix 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 23 tokens to every session and 1,520 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
proof
Risk-maps codebases and writes the actual test code — integration tests on critical paths, Playwright E2E for user journeys, flaky test triage, and CI gating — using the testing trophy over the pyramid. Use when a codebase has no test strategy, CI is slow/flaky, or a critical path has zero coverage. Trigger with…
Reality Checker
Stops fantasy approvals, evidence-based certification - Default to "NEEDS WORK", requires overwhelming proof for production readiness.
Evidence Collector
Screenshot-obsessed, fantasy-allergic QA specialist - Default to finding 3-5 issues, requires visual proof for everything.
app-test-debug-agent
A testing and debugging assistant for web applications, using browser inspection, automated browser tests, local runs, and application logs.