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 creating-custom-holoviz-skillsgit 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/creating-custom-holoviz-skills)<a href="https://agentmods.dev/skills/holoviz-dev/holoviz-skills/creating-custom-holoviz-skills"><img src="https://agentmods.dev/badge/skills/holoviz-dev/holoviz-skills/creating-custom-holoviz-skills/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/creating-custom-holoviz-skills"><img src="https://agentmods.dev/badge/skills/holoviz-dev/holoviz-skills/creating-custom-holoviz-skills.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.00048 | $0.03844 |
| Opus 5 | $0.00024 | $0.01922 |
| Sonnet 5 | $0.00010 | $0.00769 |
| Haiku 4.5 | $0.00005 | $0.00384 |
Grade A, and why
creating-custom-holoviz-skills 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 12d 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Custom Skills
Guide for adding a new skill to the holoviz-skills repository. This covers
what's specific to this repo — for general skill-authoring advice (drafting,
testing, iterating, description optimization), see the skill-creator skill.
Contents
- Deciding to add a skill
- Repo layout
- Adding a sub-skill
- SKILL.md structure
- Resource files
- Routing skills
- Docs pipeline
- Evaluation
- Resources
Deciding to add a skill
Add a skill when agents consistently get something wrong about a HoloViz library or workflow and the fix can be expressed as concise, opinionated instructions. Good candidates: API gotchas, deprecated patterns, non-obvious conventions, correct import paths, parameter names that changed between versions. Bad candidates: restating upstream docs, general Python knowledge, anything the model already handles well.
Repo layout
Skills live under one of two category directories, or at the top level for cross-cutting concerns:
developing-with-holoviz/ # Using HoloViz libraries in projects
SKILL.md # Routing skill — dispatches to sub-skills
skills/
hvplot/SKILL.md
panel/SKILL.md
...
contributing-to-holoviz/ # Maintaining HoloViz packages
SKILL.md # Routing skill
skills/
cleanup/SKILL.md
testing/SKILL.md
...
creating-custom-holoviz-skills/ # This skill (top-level, standalone)
SKILL.md
Pick the category that fits. If your skill is about using a HoloViz tool,
it goes under developing-with-holoviz/skills/. If it's about contributing
to a HoloViz package (testing, docs, releases), it goes under
contributing-to-holoviz/skills/.
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.
- 12d ago First seen · 344 lines · 48 tokens per session scan A 82a507024081
creating-custom-holoviz-skills is a skill published in the GitHub repository holoviz-dev/holoviz-skills (5 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 48 tokens to every session and 3,844 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…