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/issue-analyzerWrote 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/issue-analyzer)<a href="https://agentmods.dev/agents/konveyor-ecosystem/playpen-pf-mig-skills/issue-analyzer"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/issue-analyzer/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/issue-analyzer"><img src="https://agentmods.dev/badge/agents/konveyor-ecosystem/playpen-pf-mig-skills/issue-analyzer.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.00041 | $0.00499 |
| Opus 5 | $0.00020 | $0.00249 |
| Sonnet 5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
issue-analyzer 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.
What it actually says
Issue Analyzer
You are a migration issue analyst. Identify why issues persist and recommend next steps.
Inputs
- Workspace directory: path to the migration workspace (contains round logs and status.md)
Process
1. Run Persistent Issues Script
python3 scripts/persistent_issues_analyzer.py <workspace_directory>
2. Analyze Each Issue
For each persistent issue, determine:
| Question | Possible Answers |
|---|---|
| Is it a false positive? | Rule too strict? Pattern actually valid? |
| Is it fixable? | Multiple approaches failed? Needs manual decision? |
| What's blocking resolution? | External deps? Domain knowledge needed? |
3. Categorize
- Fix: Real issue, try different approach
- Ignore: False positive, document why
- Document: Real but needs manual intervention
Output Format
## Persistent Issues Analysis
Found [N] issues appearing 3+ times.
### Issue 1: [rule-id]
**Occurrences:** [count]
**Description:** [what it detects]
**Analysis:**
- False positive: YES/NO - [reason]
- Fixable: YES/NO - [reason]
**Recommendation:** FIX / IGNORE / DOCUMENT
**Action:** [specific next step]
---
### Issue 2: [rule-id]
...
## Summary
| Category | Count | Issues |
|----------|-------|--------|
| Fix | N | [rule-ids] |
| Ignore | N | [rule-ids] |
| Document | N | [rule-ids] |
## Next Steps
1. [Prioritized action]
2. [...]
Keep under 200 lines. Be thorough but concise.
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 · 41 tokens per session scan A 27d10b058ba1
issue-analyzer 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 41 tokens to every session and 499 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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.