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/floor/vlist/diagnose-testnpx skills add floor/vlist --skill diagnose-testgit clone --depth 1 https://github.com/floor/vlistWrote 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/floor/vlist/diagnose-test)<a href="https://agentmods.dev/skills/floor/vlist/diagnose-test"><img src="https://agentmods.dev/badge/skills/floor/vlist/diagnose-test.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.00021 | $0.00368 |
| Opus 5 | $0.00010 | $0.00184 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
diagnose-test 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
Diagnose Failing Test
Debug a failing vlist test with full context.
Instructions
-
Run the failing test:
bun test $ARGUMENTS 2>&1
-
If the test passes, report that and stop.
-
If it fails, gather context:
- Read the full test file
- Identify which source file(s) the test covers (from imports)
- Read those source files
- Read relevant test helpers if used (
test/helpers/)
-
Analyze the failure:
- What does the test expect?
- What actually happened?
- Is this a test bug or a source bug?
- If it's a recent regression, check
git log --oneline -10 -- <source-file>for recent changes
-
Output:
## Failing Test **File:** test/plugins/async/plugin.test.ts **Test:** "should cancel load when velocity exceeds threshold" **Error:** Expected 0 but received 1 ## Diagnosis The test expects `loadAdapter.load` to not be called when velocity > LOAD_VELOCITY_THRESHOLD, but the velocity check in src/features/async/feature.ts:87 uses `>=` instead of `>`. ## Suggested Fix Change line 87 from `velocity >= threshold` to `velocity > threshold`, or update the test to use a velocity strictly above the threshold. -
Be specific — include line numbers, variable names, and exact values.
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 · 48 lines · 21 tokens per session scan A cec81a3b0f58
diagnose-test is a skill published in the GitHub repository floor/vlist (16 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 368 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-09-01.
Other skills, from other repositories
poll-github-work
Poll and rank open GitHub issues, RFCs, and pull requests for maintainer work, or start one explicitly selected item. Use when a user asks what to work on, requests backlog priorities, says "poll work," wants actionable issues or pull requests, or says "start.
evalscope
LLM evaluation & inference performance testing via the evalscope CLI. Translates natural language requests into evalscope commands for: (1) Model accuracy evaluation — runs 160+ benchmarks against local checkpoints or API endpoints (OpenAI-compatible, Anthropic, LiteLLM); (2) Performance stress testing — TTFT, TPOT…
hotpath_init
Configure hotpath profiling in a Rust project. Adds the hotpath dependency with feature-gated setup, instruments main with hotpath::main, functions with measure/measureall, and wraps channels, mutexes, rwlocks, streams, futures, reqwest clients, axum routers and byte-level I/O with hotpath macros. Use when the user…
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
opentelemetry-net-instrumentation
Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.
database-performance
Database access patterns for performance. Separate read/write models, avoid N+1 queries, use AsNoTracking, apply row limits, and never do application-side joins. Works with EF Core and Dapper.