Borrowing it
Nothing to install: this file belongs to fenre/splunk-monitoring-use-cases. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fenre/splunk-monitoring-use-cases/main/AGENTS.mdgit clone --depth 1 https://github.com/fenre/splunk-monitoring-use-casesWrote 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/instructions/fenre/splunk-monitoring-use-cases/agents-md)<a href="https://agentmods.dev/instructions/fenre/splunk-monitoring-use-cases/agents-md"><img src="https://agentmods.dev/badge/instructions/fenre/splunk-monitoring-use-cases/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.
<a href="https://agentmods.dev/instructions/fenre/splunk-monitoring-use-cases/agents-md"><img src="https://agentmods.dev/badge/instructions/fenre/splunk-monitoring-use-cases/agents-md.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.06009 | $0.06009 |
| Opus 5.5 | $0.02404 | $0.02404 |
| Sonnet 5.5 | $0.01202 | $0.01202 |
| Haiku 4.5 | $0.00601 | $0.00601 |
Grade A, and why
splunk-monitoring-use-cases 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 yesterday.
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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — AI Agent Entrypoint
Start here if you are an AI agent (Cursor, Claude Code, Codex, Copilot, or any MCP-capable client) working with this repository.
Work order
Every task starts from origin/main, and its pull request is merged before the next task starts.
What this repository is
A curated, machine-readable, versioned catalog of 16,600+ IT infrastructure
monitoring use cases for Splunk, organized across 25 technology domains.
Use cases implemented on the Splunk platform carry a ready-to-run SPL query
and CIM data model mappings; use cases implemented in another Splunk product
(for example Splunk Agent Observability) carry that product's configuration as
productArtifacts instead. Every use case has criticality/difficulty ratings,
implementation guidance, and a plain-language explanation.
The catalog is content-only — it does not execute or schedule searches against a live Splunk instance.
Key entry points
| What you need | Where to look |
|---|---|
| Full product design | docs/DESIGN.md — architecture, build pipeline, field taxonomy, replication guide |
| v7 architecture | docs/architecture.md — modular build, distribution channels, stability commitments |
| Use case schema | schemas/uc.schema.json — JSON Schema 2020-12, additionalProperties: false |
| Catalog field reference | docs/catalog-schema.md — abbreviated keys → full field names and types |
| Use case field reference | docs/use-case-fields.md — authoring contract for markdown fields |
| Machine-readable catalog | catalog.json (generated) — top-level keys: DATA, CAT_META, CAT_GROUPS, EQUIPMENT, implementationRoadmap |
| Versioned JSON API | api/v1/ — compliance, OSCAL, MITRE, equipment, UC endpoints (generated) |
| MCP server | mcp/ — splunk-uc-mcp Python package; 14 tools, 4 URI schemes; docs/mcp-server.md |
| LLM-readable indices | llms.txt, llms-full.txt (generated by build.py; available at the GitHub Pages URL) |
| Per-UC markdown twin | /uc/UC-X.Y.Z/uc.md — pure-markdown rendering of one UC, stamped with Last-modified and Catalogue-version. Always advertised on the HTML page via <link rel="alternate" type="text/markdown"> and on the JSON twin via the markdown URL field. |
| Prompt recipes | AGENTS-EXAMPLES.md — copy-paste prompts for MCP, JSON-API, and bare-LLM workflows |
| AI usage policy | ai.txt (also at /.well-known/ai.txt) — license, attribution preference, accuracy guidance |
| Changelog | CHANGELOG.md — Keep a Changelog format |
| Version | VERSION — single source of truth for the release number |
| Catalogue health snapshot | dist/metrics.json (generated, schema schemas/v2/metrics.schema.json) — top-line counts, quality-tier rollups, depth percentiles, coverage, and Top-N leaderboards. Trend-friendly across releases via data/metrics-history/. |
| Bibliographic database | data/source-references.json — 124 curated, APA-formatted source records (regulations, standards, vendor docs, RFCs, books) consumed by the doc-footer generator. Stable IDs are permanent contracts. |
| Per-doc citation mappings | data/source-mappings.json — explicit Primary / Supporting / Related source IDs for documented topics; _topic_keywords heuristics fill guides without explicit entries. |
| Inline citation phrases | data/inline-citation-phrases.json — phrase → source-ID map. The footer generator scans each doc for the first mention of each cited source and injects <sup>[N]</sup> markers linked to the bibliography. |
| External link health | data/source-links-status.json (generated by scripts/check_source_links.py) — last-known HTTP status of every URL in the bibliography. Run on demand or in scheduled CI; bot-blocked vendor portals are reported separately. |
| Auto-generated docs registry | data/auto-generated-docs.json — every doc whose body is overwritten by a CI script, with its generator command, inputs, and refresh cadence. Enforced by scripts/audit_auto_gen_provenance.py. |
| Build telemetry | dist/build-telemetry.json (generated only on non-reproducible builds, schema schemas/v2/build-telemetry.schema.json) — per-stage wall-clock duration for the build pipeline. |
| Starter packs (guided onboarding) | data/starter-packs/ (source, schema schemas/starter-pack.schema.json) → api/v1/starter-packs/ (generated by python -m splunk_uc generate-starter-packs). Short, ordered UC lists per goal and technology, surfaced by the site's "Start here" wizard (#start) and the plan_rollout MCP tool. Guide: docs/starter-packs.md. |
| Stewardship digest | dist/stewardship-digest.{json,md} (generated on demand, schema schemas/v2/stewardship-digest.schema.json) — release-over-release deltas (counts, quality-tier mix, coverage, top movers in regulations / MITRE / CIM / equipment leaderboards), open audit warnings, and stale-UC backlog. Run make stewardship-digest when a snapshot is wanted. |
| Equipment app map | data/equipment-app-map.json — curated slug → Splunkbase[7] add-ons + DSA ingest ids for the equipment picker; schema schemas/equipment-app-map.schema.json; authoring guide docs/equipment-app-map.md. Regenerate with python3 -m splunk_uc generate-equipment-app-map; gated by audit-equipment-app-map --check. |
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.
- yesterday Changed · +1 lines · +65 tokens per session a60f8d877884
- 3d ago Changed b2d630d729fe
- 4d ago Changed · +14 lines · +574 tokens per session 92ef11cddb15
- 10d ago Changed · +14 lines · +467 tokens per session 0f67d1c3de2f
- 2mo ago Changed · +6 lines · +309 tokens per session 344832f47098
- 2mo ago First seen · 239 lines · 4,594 tokens per session scan A 2c7a57806a16
splunk-monitoring-use-cases AGENTS.md is an instructions file published in the GitHub repository fenre/splunk-monitoring-use-cases (11 stars, last pushed yesterday), licensed MIT. It adds 6,009 tokens to every session, about $0.0240 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-31.
splunk-monitoring-use-cases AGENTS.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| splunk-monitoring-use-cases AGENTS.mdfenre/splunk-monitoring-use-cases | Instructions file | 11 | yesterday | MIT | A | 6,009 | Codex, OpenCode |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | today | MIT | A | 7,461 | Codex, OpenCode |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 5,516 | GitHub Copilot |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | yesterday | MIT | A | 4,680 | Codex, OpenCode |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 3,093 | GitHub Copilot |
| vscode ai-customization.instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 1,907 | GitHub Copilot |