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/rcastley/splunk-custom-visualizations/splunk-viznpx skills add rcastley/splunk-custom-visualizations --skill splunk-vizgit clone --depth 1 https://github.com/rcastley/splunk-custom-visualizationsWrote 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/rcastley/splunk-custom-visualizations/splunk-viz)<a href="https://agentmods.dev/skills/rcastley/splunk-custom-visualizations/splunk-viz"><img src="https://agentmods.dev/badge/skills/rcastley/splunk-custom-visualizations/splunk-viz.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.1 | $0.00127 | $0.01562 |
| Opus 5 | $0.00063 | $0.00781 |
| Sonnet 5 | $0.00025 | $0.00312 |
| Haiku 4.5 | $0.00013 | $0.00156 |
Grade A, and why
splunk-viz 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 6d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Splunk Custom Visualizations
Generate production-ready Canvas 2D custom visualizations for both Splunk frameworks.
Select the framework first
Determine the framework before creating or changing files. Do not mix lifecycle, configuration, build, or harness conventions.
| Target | Select when | Runtime and configuration |
|---|---|---|
| Native Dashboard Studio | Create a new visualization specifically for Dashboard Studio on Splunk 10.4+ | Sandboxed iframe, @splunk/dashboard-studio-extension, config.json, ES modules, esbuild, .spl package |
| Legacy custom visualization | Support Simple XML, Search, saved reports, an existing SplunkVisualizationBase app, or pre-10.4 deployments |
Backbone/AMD, SplunkVisualizationBase, formatter.html, webpack, legacy app package |
| Both outputs | The user explicitly needs both frameworks | Separate framework adapters around shared rendering and normalization modules; independent packages and tests |
For a vague new Dashboard Studio request, recommend the native Studio framework. Do not call a legacy visualization that happens to render in Dashboard Studio a native Studio extension.
Confirm or infer:
- Target framework: native Studio, legacy, or both outputs.
- Minimum Splunk version and deployment target: Enterprise, Cloud, or both.
- Visualization ID, label, description, author, required and optional SPL fields, settings, drilldowns, tokens, and no-data behavior.
- Native Studio template: JavaScript, TypeScript, React, or React + TypeScript. Prefer TypeScript for new work; use React only when component state or UI composition justifies it.
Route to the required references
Native Dashboard Studio
Read before editing:
references/studio-framework.md— required project, API, configuration, packaging, and verification workflowreferences/studio-canvas-template.md— required for framework-agnostic JavaScript or TypeScript Canvas visualizationsreferences/studio-react-template.md— required only for React or React + TypeScriptreferences/studio-harness.md— required whenever creating or changing native Studio test coverage
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 241 B
- assets/dashboard-app-build.sh 7.5 KB runs code
- references/canvas-recipes.md 4.4 KB
- references/core-template.md 9.8 KB
- references/custom-fonts.md 3.5 KB
- references/dashboard-studio-app.md 8.2 KB
- references/design-guidelines.md 4.9 KB
- references/drilldown.md 3.4 KB
- references/legacy-framework.md 3.9 KB
- references/legacy-harness.md 3.6 KB
- references/legacy-packaging.md 2.7 KB
- references/legacy-runtime.md 4.5 KB
- references/legacy-scaffold.md 5.0 KB
- references/smoothing.md 4.8 KB
- references/studio-canvas-template.md 7.8 KB
- references/studio-framework.md 12 KB
- references/studio-harness.md 6.9 KB
- references/studio-react-template.md 3.3 KB
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.
- 6d ago First seen · 126 lines · 127 tokens per session scan A a0c76792e156
splunk-viz is a skill published in the GitHub repository rcastley/splunk-custom-visualizations (41 stars, last pushed 3d ago), licensed Apache-2.0. It adds 127 tokens to every session and 1,562 once invoked, about $0.0006 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-30.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…