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 skills add holoviz-dev/holoviz-skills --skill testinggit clone --depth 1 https://github.com/holoviz-dev/holoviz-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/holoviz-dev/holoviz-skills/testing)<a href="https://agentmods.dev/skills/holoviz-dev/holoviz-skills/testing"><img src="https://agentmods.dev/badge/skills/holoviz-dev/holoviz-skills/testing/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/holoviz-dev/holoviz-skills/testing"><img src="https://agentmods.dev/badge/skills/holoviz-dev/holoviz-skills/testing.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.00034 | $0.00826 |
| Opus 5.5 | $0.00014 | $0.00330 |
| Sonnet 5.5 | $0.00007 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
testing 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
This skill covers testing patterns and edge cases specific to HoloViz repositories.
Contents
General Guidelines
- Run tests via pixi. Check
pixi.tomlfor tasks (e.g.pixi run test-unit,pixi run test-ui). - New tests must fail on
mainbefore submitting, since a test that passes without the fix doesn't test the fix. - Write tests from the issue or the expected behavior, not from what the new code does. A test written to match the implementation checks the author's assumptions, so it can pass on the very bug it was meant to catch. Agents tend to write this kind of test for their own code.
- Never change a test's expected value just to make it pass. Change it only after confirming the new output is correct, and say why in the PR, since editing the expectation to match wrong output hides the regression the test caught.
- UI tests require the
--uiflag. - Only create a new test file if no existing file is a good fit, so tests for one module stay in one place and the next contributor finds them.
- Cover the lines you add; exercise new behavior, don't just import it.
Edge Cases and Logical Errors
- Identify logical errors and edge cases in the changed code. Trace branching logic and boundary conditions to find inputs that could produce wrong results, silent data loss, or unexpected exceptions.
- Test for NaN and datetime types (np, pd) — these are common edge cases across HoloViz that are easy to miss.
- Also probe (where the logic branches on them): empty/single-element inputs, duplicate/colliding labels, negative/reversed values, unsorted input.
- Parameterize tests when the same logic is exercised with different inputs.
- Name tests for intent. Put what the test covers and why — including any issue link — in the function docstring, not a leading
#comment: the docstring travels with the test inpytest -voutput. Reserve#for a genuinely non-obvious step in the body, and skip comments that just restate what the test does.
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 Changed · +2 lines 3413371ff5f3
- 2mo ago First seen · 66 lines · 34 tokens per session scan A 68db8858be06
testing is a skill published in the GitHub repository holoviz-dev/holoviz-skills (5 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 34 tokens to every session and 826 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.
testing compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| testingholoviz-dev/holoviz-skills | Skill | 5 | 2d ago | BSD-3-Clause | A | 34 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |