testing

testing is a skill for Claude Code, Codex from holoviz-dev/holoviz-skills. It costs 34 tokens per session (692 once invoked), scanned A, original, BSD-3-Clause.

A testing guide for HoloViz Python packages, including practices for writing tests and checking edge cases. Edge cases are unusual inputs such as empty data, missing values, or reversed ranges.

In plain words
What is it for?
Use it when writing or reviewing tests, checking coverage, testing user interfaces, or examining inputs such as NaN values, dates, duplicates, and unsorted data.
Why use it?
It helps catch incorrect results, silent data loss, and unexpected errors before code is submitted for review.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when writing or reviewing tests, checking coverage, testing user interfaces, or examining inputs such as NaN values, dates, duplicates, and unsorted data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/holoviz-dev/holoviz-skills/testing
Install

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.

Any agent
npx skills add holoviz-dev/holoviz-skills --skill testing
Clone the repo
git clone --depth 1 https://github.com/holoviz-dev/holoviz-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/holoviz-dev/holoviz-skills/testing.svg)](https://agentmods.dev/skills/holoviz-dev/holoviz-skills/testing)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 692 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00692
Opus 5 $0.00017 $0.00346
Sonnet 5 $0.00007 $0.00138
Haiku 4.5 $0.00003 $0.00069

Measured 7d ago against content hash 68db8858be06, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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 7d 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.

contributing-to-holoviz/skills/testing/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 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.toml for tasks (e.g. pixi run test-unit, pixi run test-ui).
  • New tests must fail on main before submitting.
  • UI tests require the --ui flag.
  • Only create a new test file if no existing file is a good fit.
  • 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 in pytest -v output. Reserve # for a genuinely non-obvious step in the body, and skip comments that just restate what the test does.
# WRONG — only tests the happy path
def test_filter_by_range():
    df = pd.DataFrame({'x': [1, 2, 3]})
    result = filter_by_range(df, 'x', low=1, high=3)
    assert len(result) == 3

# CORRECT — covers edge cases and logical boundaries
@pytest.mark.parametrize(
    ("data", "low", "high", "expected_len"),
    [
        ([1, 2, 3], 1, 3, 3),
        ([1, 2, 3], 2, 2, 1),
        ([1, 2, 3], 5, 10, 0),
        ([], 0, 1, 0),
        ([np.nan, 1, 2], 0, 2, 2),
        ([1, 2, None], 0, 2, 2),
    ],
    ids=[
        "inclusive_bounds",
        "single_value_range",
        "no_matches",
        "empty_input",
        "nan_values",
        "none_values",
    ],
)
def test_filter_by_range(data, low, high, expected_len):
    df = pd.DataFrame({'x': data})
    result = filter_by_range(df, 'x', low=low, high=high)
    assert len(result) == expected_len

Read the full file on GitHub · 66 lines

Changes

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.

  1. 7d ago First seen · 66 lines · 34 tokens per session scan A 68db8858be06

Subscribe to this mod's changes

testing is a skill published in the GitHub repository holoviz-dev/holoviz-skills (5 stars, last pushed 6d ago), licensed BSD-3-Clause. It adds 34 tokens to every session and 692 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.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens