Borrowing it
Nothing to install: this file belongs to vepo/issues. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vepo/issues/main/.claude/skills/fix-tests/SKILL.mdgit clone --depth 1 https://github.com/vepo/issuesWrote 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/vepo/issues/fix-tests)<a href="https://agentmods.dev/skills/vepo/issues/fix-tests"><img src="https://agentmods.dev/badge/skills/vepo/issues/fix-tests/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/skills/vepo/issues/fix-tests"><img src="https://agentmods.dev/badge/skills/vepo/issues/fix-tests.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.00025 | $0.00393 |
| Opus 5.5 | $0.00010 | $0.00157 |
| Sonnet 5.5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
fix-tests 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 1mo 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
You are an expert Java developer. Fix all failing tests in the Issues project.
Follow .cursor/rules/issues-testing.mdc and .cursor/rules/issues-test-failure-diagnosis.mdc.
Follow this exact loop — do not ask for confirmation and do not invent workarounds.
-
Discover failures
mvn testIf frontend may be affected, also run:
cd src/main/webui && npm test -- --no-watch --browsers=ChromeHeadless -
Check for failures
- If no test failures, run
mvn verify. If green, print✅ All tests pass!and stop. - Otherwise proceed to step 3.
- If no test failures, run
-
List each failing test with the reason Parse
target/surefire-reports/*.txt. Group failures by root cause. For each:- Test class & method name
- Exception type and stack trace
- Assertion details (expected vs actual)
-
Fix each root cause (one at a time)
- Read
ARCHITECTURE.mdand the test + production code. - Apply a direct fix — never
Thread.sleep(),@Disabled, or swallowed exceptions. - Re-run:
mvn test -Dtest=ClassName#methodName
- Read
-
Repeat steps 3–4 until tests pass, then run
mvn verifyonce.
After fix is green: write one report under reports/ per .cursor/rules/issues-test-failure-diagnosis.mdc.
Start the loop now.
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.
- 1mo ago First seen · 42 lines · 25 tokens per session scan A 58ae720f6444
fix-tests is a skill published in the GitHub repository vepo/issues (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 393 once invoked, about $0.0001 per session on Opus 5.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
Karma Testing
Comprehensive Karma test runner skill for browser-based JavaScript unit testing with Jasmine, Mocha, or QUnit frameworks, real browser execution, coverage reporting, and CI/CD pipeline integration.
flutter-bloc-state-management
Implement BLoC/Cubit state, events, transitions, and async concurrency in Flutter. Use for BLoC/Cubit feature logic, debounced/cancellable events, state rendering, or bloc tests—not generic widget-only work.
authoring-benchmarks
Design, implement, run, debug, and interpret browser performance benchmarks for Elements components and utilities. Use whenever the user asks to benchmark or performance-test runtime code, create or update a .test.bench.ts file, compare benchmark results, investigate a browser performance regression, understand Vitest…
archunit-rules
Encode architecture invariants as ArchUnit rules. Use when defining or reviewing layer boundaries, package dependencies, naming conventions, or cross-module access.
jacoco-coverage-policy
JaCoCo configuration and policy enforcement — 90% line+branch floor, 95% target, 95% on new code. Use when wiring JaCoCo into the Maven build or interpreting jacoco.xml.
chart-defaults
Find the actual runtime default value of any AG Charts configuration option, and keep JSDoc Default: markers accurate. Use when documenting a default, verifying a change has not altered one, writing tests against default behaviour, or auditing whether a TypeScript comment matches the theme template.