splunk-validator

A validator for Splunk security detections, which are rules that look for suspicious activity in Splunk data. It checks detections after they have been executed.

In plain words
What is it for?
Use it to verify Splunk detections after execution; it is intended for Splunk rather than other security-monitoring platforms.
Why use it?
It helps confirm that a Splunk detection actually triggers as expected instead of relying only on its written query or design.

Agent for Cursor

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.

agentmods
npx agentmods add agents/threadlinqs-cmd/threadlinqs-security-detection-mcp/splunk-validator
Clone the repo
git clone --depth 1 https://github.com/threadlinqs-cmd/Threadlinqs-Security-Detection-MCP

Made for: Cursor.

Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,025 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00038 $0.01025
Opus 5 $0.00019 $0.00513
Sonnet 5 $0.00008 $0.00205
Haiku 4.5 $0.00004 $0.00103

Measured 2d ago against content hash 0245ce85c36f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

splunk-validator 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 2d 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.

.cursor/agents/splunk-validator.md · 136 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2d ago First seen · 136 lines · 38 tokens per session scan A 0245ce85c36f

Subscribe to this mod's changes

splunk-validator is an agent published in the GitHub repository threadlinqs-cmd/Threadlinqs-Security-Detection-MCP (1 stars, last pushed 5mo ago), with no licence file. It adds 38 tokens to every session and 1,025 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.