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/vepo/issues/fix-testsnpx skills add vepo/issues --skill fix-testsgit clone --depth 1 https://github.com/vepo/issuesWhat 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.00025 | $0.00393 |
| Opus 5 | $0.00013 | $0.00197 |
| Sonnet 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 2d 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.
- 2d 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 1mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 393 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 skills, from other repositories
test-writer
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines.
create-test
Generate or update unit tests for a component following project testing conventions.
testing
Test Radix NG primitives across every layer and pick the RIGHT one for a change: Vitest unit (zoneless), jest-axe a11y, Playwright browser regression (apps/visual-regression), SSR (apps/radix-ssr-testing), and perf benches (apps/radix-perf-testing). Enforces the rule that layout / positioning / part-visibility /…
authoring-projects
Author a new standalone NVIDIA Elements workspace project containing a Lit component, including package files, the five test types, Wireit tasks, workspace and CI registration, metadata generation, documentation-site integration, dependency-lint configuration, and generated lock/notice files. Use when creating or…
authoring-tests
Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks…
vitest-auto-spy
Write or fix tests that use vitest-auto-spy — typed spies generated from a class or a type on Vitest, bun:test and node:test. Use when a spec imports vitest-auto-spy or any of its subpaths (/angular, /bun-angular, /bun, /node, /rxjs, /nestjs, /setup, /zone, /eslint-plugin), when the user mentions createSpyFromClass…