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/kangwonland/splunk-skill/splunk-envnpx skills add Kangwonland/splunk-skill --skill splunk-envgit clone --depth 1 https://github.com/Kangwonland/splunk-skillWrote 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/kangwonland/splunk-skill/splunk-env)<a href="https://agentmods.dev/skills/kangwonland/splunk-skill/splunk-env"><img src="https://agentmods.dev/badge/skills/kangwonland/splunk-skill/splunk-env.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 | $0.00152 | $0.01356 |
| Opus 5 | $0.00076 | $0.00678 |
| Sonnet 5 | $0.00030 | $0.00271 |
| Haiku 4.5 | $0.00015 | $0.00136 |
Grade A, and why
splunk-env 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 4d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Splunk Environment Metadata Configuration
This skill manages env-config.md — a pre-filled configuration file where users
register their Splunk environment (indexes, sourcetypes, hosts, lookups, macros).
The splunk-spl skill reads this file to generate environment-specific SPL.
How It Works
- User edits
env-config.mdin this skill directory with their environment info - When generating SPL, the splunk-spl skill reads env-config.md automatically
- SPL is generated with the correct index names, sourcetypes, and field names
Without env-config.md (generic):
index=main sourcetype=firewall action=blocked
| stats count by src_ip
With env-config.md (environment-specific):
index=sec_logs sourcetype=pan:traffic action=blocked
| stats count by src_ip
| lookup asset_db.csv ip AS src_ip OUTPUT hostname, owner
env-config.md
The configuration file is at env-config.md in this skill's directory.
It ships with example data — the user replaces it with their own environment.
When this skill is triggered:
- Find the
env-config.mdfile path using Glob (**/splunk-env/env-config.md). - Show the user the full path so they know where to edit it directly.
- Read the file to understand the current configuration.
- Help the user edit it: add, modify, or remove entries as requested.
- Write the updated file back.
Always tell the user the file path, e.g.:
"Your Splunk environment config is at:
/path/to/splunk-env/env-config.mdYou can edit this file directly anytime, or tell me what to change."
File Structure
The file uses markdown tables organized by category:
| Section | Required | What It Contains |
|---|---|---|
| Metadata | Yes | Deployment type, indexer/SH count, version |
| Indexes | Yes | Name, purpose, sourcetypes, use-when scenarios |
| Sourcetypes | Yes | Name, indexes, category, vendor/product |
| SPL Generation Notes | Yes | Scenario → index+sourcetype mappings |
| Hosts & Host Groups | Recommended | Key hosts and naming patterns |
| Lookups | Optional | Name, type, key/output fields |
| Macros | Optional | Name, definition, args |
| Data Models | Optional | Name, acceleration, datasets |
What ships with it
5 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.
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.
- 4d ago First seen · 161 lines · 152 tokens per session scan A 44ad32020a19
splunk-env is a skill published in the GitHub repository Kangwonland/splunk-skill (5 stars, last pushed 4mo ago), licensed MIT. It adds 152 tokens to every session and 1,356 once invoked, about $0.0008 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…