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 skills/eea/eea.agent.skills/quality-fixesnpx skills add eea/eea.agent.skills --skill quality-fixesgit clone --depth 1 https://github.com/eea/eea.agent.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/skills/eea/eea.agent.skills/quality-fixes)<a href="https://agentmods.dev/skills/eea/eea.agent.skills/quality-fixes"><img src="https://agentmods.dev/badge/skills/eea/eea.agent.skills/quality-fixes.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.00032 | $0.01088 |
| Opus 5 | $0.00016 | $0.00544 |
| Sonnet 5 | $0.00006 | $0.00218 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
quality-fixes 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Fixes
Use this skill when a repository already fails lint, typing, tests, Docker verification, or Jenkins quality gates and you need to repair it until the real blocking commands pass.
When to use
Use this skill when:
- a repo fails Ruff, Black, ESLint, mypy, tsc, pytest, Playwright, Cypress, or similar checks
- a Docker-based
Dockerfile.testverification path fails - a Jenkins pipeline already exists and the code does not pass it
- the Jenkins skill preflight finds existing failures before creating a new Jenkinsfile
Primary goal
Repair the code and supporting configuration until the same commands used by Jenkins or CI pass, while keeping changes as small and explainable as possible.
Required workflow
- Run the failing commands exactly as the repository or Jenkins would run them.
- Capture the real failures, not guessed failures.
- Classify them into:
- safe auto-fixable issues
- direct code repair issues
- environment / dependency / Docker path issues
- Apply safe auto-fixes first.
- Repair remaining code or config problems directly.
- Rerun the same commands.
- Stop only when the real blocking commands pass.
Safe auto-fix first
Try mechanical rewrites before manual code edits when they are safe:
ruff check --fixruff formatblackisortprettier --writeeslint --fixfor safe repository-approved rules
Do not claim the repository is fixed just because auto-fix changed files. Always rerun the failing commands.
Repair categories
1. Lint/config debt
Examples:
- import ordering
- formatting drift
- docstring policy failures
- unused imports
- line length issues
2. Type-check failures
Examples:
- missing annotations required by repo policy
- bad return types
- incorrect optional handling
- missing stubs or import configuration
3. Test failures
Examples:
- broken business logic
- invalid fixtures
- outdated assertions
- file path assumptions
- API behavior mismatches
4. Docker/CI path failures
Examples:
- broken
Dockerfile.test - inconsistent dependency definitions
- package manager conflicts
- missing binaries in the test image
- report paths that Jenkins expects but code does not produce
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 156 lines · 32 tokens per session scan A afab005a472f
quality-fixes is a skill published in the GitHub repository eea/eea.agent.skills (2 stars, last pushed 28d ago), licensed MIT. It adds 32 tokens to every session and 1,088 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…