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 skills add splunk/splunk-agent-skills --skill field-extraction-and-cim-mappinggit clone --depth 1 https://github.com/splunk/splunk-agent-skillsWrote 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/splunk/splunk-agent-skills/field-extraction-and-cim-mapping)<a href="https://agentmods.dev/skills/splunk/splunk-agent-skills/field-extraction-and-cim-mapping"><img src="https://agentmods.dev/badge/skills/splunk/splunk-agent-skills/field-extraction-and-cim-mapping/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/skills/splunk/splunk-agent-skills/field-extraction-and-cim-mapping"><img src="https://agentmods.dev/badge/skills/splunk/splunk-agent-skills/field-extraction-and-cim-mapping.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.00125 | $0.01912 |
| Opus 5 | $0.00063 | $0.00956 |
| Sonnet 5 | $0.00025 | $0.00382 |
| Haiku 4.5 | $0.00013 | $0.00191 |
Grade A, and why
field-extraction-and-cim-mapping 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 10d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Field Extraction and CIM Mapping
Produce documentation-backed, evidence-bound guidance for search-time field extraction and CIM normalization. Draft text artifacts only. Never authenticate to, modify, install on, or deploy to a Splunk environment.
Prerequisites
Record or ask for only the missing items material to the requested decision:
- representative sanitized raw events, including meaningful edge cases;
- sourcetype and relevant current
props.conf,transforms.conf, SPL, aliases, calculated fields, lookups, event types, and tags; - desired source fields and their meanings;
- target CIM dataset and installed CIM version or model details;
- Splunk product/version, persistence scope, app context, and deployment topology when configuration or routing depends on them; and
- observed field/search/data-model validation output when diagnosing or claiming validation.
Never invent event structure or field meaning. With partial evidence, first
preserve and assess every supported object-level fact. Mark each absent field
or artifact unknown, and gate only the conclusion it affects; missing context
must not erase supplied evidence. Clearly separate supplied observations,
documented facts, assumptions, provisional conclusions, and unverified steps.
When to Use
Use this skill when the primary outcome is documented extraction guidance, an evidence-bound extraction draft, a semantic CIM mapping, validation steps, or a normalization-gap diagnosis. Apply the boundaries below to adjacent work.
Workflow Overview
1. Select the extraction mechanism
Read public-guidance.md. Identify the documented
mechanism that fits the event shape: automatic key-value extraction, regex or
delimiter extraction, inline EXTRACT, reusable REPORT plus
transforms.conf, or an ad hoc SPL command. Separate persistent knowledge
objects from search-local SPL. Treat index-time extraction as a
performance-sensitive exception, not the default.
What ships with it
2 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.
- 10d ago First seen · 201 lines · 125 tokens per session scan A 4af436f6acfd
field-extraction-and-cim-mapping is a skill published in the GitHub repository splunk/splunk-agent-skills (29 stars, last pushed 19d ago), licensed Apache-2.0. It adds 125 tokens to every session and 1,912 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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…