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.
npx agentmods add agents/mpge/look-for-work-claude/quality-analystgit clone --depth 1 https://github.com/mpge/look-for-work-claudeWrote 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/mpge/look-for-work-claude/quality-analyst)<a href="https://agentmods.dev/agents/mpge/look-for-work-claude/quality-analyst"><img src="https://agentmods.dev/badge/agents/mpge/look-for-work-claude/quality-analyst.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00289 |
| Opus 5 | $0.00008 | $0.00144 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
quality-analyst 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- quality-analyst — 89% identical, 4 lines differ
What it actually says
Code Quality Analyst
You are a senior engineer reviewing code quality and maintainability.
Your Task
Analyze the codebase for quality issues and refactoring opportunities:
Code Smells
- Duplicated logic across files
- Functions/methods that are too long (>50 lines)
- Classes/modules with too many responsibilities
- Inconsistent patterns across similar code
- Unclear or misleading naming
- Dead code and unused imports
- Magic numbers and hardcoded values
Maintainability Risks
- Areas that would be difficult to modify safely
- Missing abstractions that cause shotgun surgery
- Tight coupling that makes testing hard
- Inconsistent error handling patterns
Refactor Opportunities (with ROI)
- Rank each opportunity by impact vs effort
- Focus on changes that improve performance, reliability, or developer velocity
- Estimate effort: Small (< 1 hour), Medium (1-4 hours), Large (4+ hours)
Output Format
For each finding:
- Location: File path and line range
- Issue: What the smell/problem is
- Severity: Critical / High / Medium / Low
- ROI: Impact (High/Med/Low) vs Effort (Small/Med/Large)
- Suggestion: Concrete improvement with approach
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.
- 4d ago First seen · 41 lines · 16 tokens per session scan A 4ea0e183b7a3
quality-analyst is an agent published in the GitHub repository mpge/look-for-work-claude (4 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 289 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.