agentmods.dev

splunk-custom-visualizations: Instructions file for Codex

AGENTS.md

splunk-custom-visualizations AGENTS.md is an instructions file for Codex, OpenCode from rcastley/splunk-custom-visualizations. It costs 705 tokens per session, scanned A, original, Apache-2.0.

Development instructions and examples for building custom visualizations in Splunk, a platform for searching and displaying machine data.

In plain words
What is it for?
They guide the creation, testing, and packaging of legacy Splunk visualizations and native Dashboard Studio extensions, including their build files and browser test harnesses.
Why use it?
They help developers avoid mixing Splunk's older visualization system with its newer Dashboard Studio system, which use different structures and rules.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions Codex.

This is rcastley/splunk-custom-visualizations's own configuration. It tells Codex and OpenCode how to work on splunk-custom-visualizations itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything splunk-custom-visualizations configures →

not rated 79repo changed 1mo ago A scan 705 tokens original Apache-2.0
View source ↗ rcastley/splunk-custom-visualizations
Reuse

Borrowing it

Nothing to install: this file belongs to rcastley/splunk-custom-visualizations. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rcastley/splunk-custom-visualizations/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/rcastley/splunk-custom-visualizations

Made for: Codex, OpenCode.

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 splunk-custom-visualizations AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rcastley/splunk-custom-visualizations/agents-md/github.svg)](https://agentmods.dev/instructions/rcastley/splunk-custom-visualizations/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/rcastley/splunk-custom-visualizations/agents-md"><img src="https://agentmods.dev/badge/instructions/rcastley/splunk-custom-visualizations/agents-md/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.

agentmods 80×15 button for splunk-custom-visualizations AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/rcastley/splunk-custom-visualizations/agents-md"><img src="https://agentmods.dev/badge/instructions/rcastley/splunk-custom-visualizations/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 705 This file is loaded in full into every session.
When invoked 705 The same file — it is already loaded in full.
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.00705 $0.00705
Opus 5.5 $0.00282 $0.00282
Sonnet 5.5 $0.00141 $0.00141
Haiku 4.5 $0.00071 $0.00071

Measured 1mo ago against content hash 3325a4604439, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

splunk-custom-visualizations AGENTS.md 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.

AGENTS.md · 33 lines

How it starts

The opening of the file, as written. The whole thing — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Instructions — Splunk Custom Visualizations

This repo contains a portable Agent Skill for both the native Dashboard Studio extension framework and the legacy Splunk visualization framework, plus working examples and local harnesses.

Key Paths

  • Canonical skill: .agents/skills/splunk-viz/SKILL.md — the full portable skill definition
  • Claude adapter: .claude/skills/splunk-viz/SKILL.md — discovery wrapper only
  • Cursor adapter: .cursor/skills/splunk-viz/SKILL.md — discovery wrapper only
  • Skill install: ./install-skill.sh — copy the skill into Claude, Cursor, or Codex (user-global or --project)
  • Studio examples: studio-examples/ — native Dashboard Studio extension projects
  • Studio build: ./scripts/build-studio.sh [project] or npm run build:studio
  • Harness landing: harness/index.html — local / GitHub Pages entry (/ redirects here)
  • Studio harness: harness/studio/ — iframe/API harness for built Studio bundles
  • Legacy examples: legacy/examples/ — standalone SplunkVisualizationBase apps
  • Legacy build: ./legacy/build.sh [app_name] or ./build.sh [app_name]
  • Legacy harness: harness/legacy/

Rules

  • Select the framework before creating files; never mix legacy and native Studio lifecycle or configuration conventions
  • Prefer native Studio for new Dashboard Studio work. Use legacy only for Simple XML, Search, saved reports, existing SplunkVisualizationBase apps, or pre-10.4 deployments
  • Native Studio projects use the directory structure generated by @splunk/create --mode=dashboard-studio-extension and live in studio-examples/
  • Legacy visualizations go in legacy/examples/{app_name}/ and use legacy/build.sh
  • Use ES5 syntax only in legacy visualization_source.js; native Studio entries use the generated ES2017/esbuild target
  • Always handle HiDPI, null ctx, and zero-size canvas
  • Keep visualization.css background transparent by default
  • For native Studio vizs, every editor option must appear in config.json optionsSchema, code fallbacks must match schema defaults, and result data must support the columnar shape
  • For legacy vizs, every setting in formatter.html must appear in savedsearches.conf.spec, JS defaults must match formatter defaults, and formatData must not read config
  • Use the framework-specific harness: Studio bundles in harness/studio/, legacy source in harness/legacy/
  • Package native Studio vizs with the scripts generated by the official CLI; build every Studio example from the root with ./scripts/build-studio.sh. Package legacy vizs with ./legacy/build.sh
  • Keep native Studio facts aligned with custom-visualization-builder. That official skill is Studio-only (Yarn, interactive @splunk/create, SPL.md, Cloud ACS). This repository remains dual-framework and uses npm plus README.md for the checked-in examples

Read the full file on GitHub · 33 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. 1mo ago Changed · +3 lines · +147 tokens per session 3325a4604439
  2. 1mo ago Changed · +4 lines · +115 tokens per session 87a52c6f69d7
  3. 2mo ago First seen · 26 lines · 443 tokens per session scan A ec2536103721

Subscribe to this mod's changes

splunk-custom-visualizations AGENTS.md is an instructions file published in the GitHub repository rcastley/splunk-custom-visualizations (79 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 705 tokens to every session, about $0.0028 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-30.

Analytics and metricsFrontend
Related

splunk-custom-visualizations AGENTS.md compared with instructions from other repositories

splunk-custom-visualizations AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
splunk-custom-visualizations AGENTS.mdrcastley/splunk-custom-visualizationsInstructions file791mo agoApache-2.0A705Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode