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 license-and-capacity-planning-advisorgit 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/license-and-capacity-planning-advisor)<a href="https://agentmods.dev/skills/splunk/splunk-agent-skills/license-and-capacity-planning-advisor"><img src="https://agentmods.dev/badge/skills/splunk/splunk-agent-skills/license-and-capacity-planning-advisor/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/license-and-capacity-planning-advisor"><img src="https://agentmods.dev/badge/skills/splunk/splunk-agent-skills/license-and-capacity-planning-advisor.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.00040 | $0.02907 |
| Opus 5.5 | $0.00016 | $0.01163 |
| Sonnet 5.5 | $0.00008 | $0.00581 |
| Haiku 4.5 | $0.00004 | $0.00291 |
Grade A, and why
license-and-capacity-planning-advisor 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.
How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Splunk License and Capacity Planning Advisor
Separate entitlement validity and lifecycle work from capacity sizing before recommending action. A report that an entitlement is invalid or expired is a lifecycle signal; it does not prove that measured demand exceeds licensed capacity. Likewise, high measured use does not establish that an entitlement is invalid.
This skill is advisory-only. Ground product behavior in current official Splunk documentation, make assumptions explicit, never invent quantities, and route contract, renewal, pricing, or purchase decisions to the authorized licensing or commercial owner.
Prerequisites
Start with the user's sanitized facts. Do not require customer, account, case, stack, credential, or commercial-term identifiers. Collect only the facts that change the classification or plan.
For an entitlement or lifecycle report, ask for:
- Splunk Enterprise release and deployment type;
- the exact sanitized status or error text and where it was observed;
- the applicable license type and licensed metric, if known;
- the relevant effective or expiration date as shown by an authorized source;
- who owns the entitlement record and who is authorized to install or renew it.
For capacity sizing, ask for:
- the licensed metric that actually applies, such as ingest volume or infrastructure vCPU, confirmed against current documentation and the entitlement owner;
- recent measured use from a representative period, including peaks and normal variability;
- the forecast horizon and the method or assumptions behind the forecast;
- planned workload changes, timing, and expected contribution to the same licensed metric; and
- the current licensed quantity and any owner-approved planning threshold.
If those capacity facts are absent, do not produce a number or purchase recommendation. Give a collection plan instead.
Internet access is required for substantive current product claims. Prefer the most specific current official Splunk page for the identified release and licensed metric. If browsing is unavailable, label supplied URLs as unverified guidance leads and state that version applicability remains open.
What ships with it
1 file 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.
- 1mo ago First seen · 327 lines · 40 tokens per session scan A a74b1aff9286
license-and-capacity-planning-advisor is a skill published in the GitHub repository splunk/splunk-agent-skills (62 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,907 once invoked, about $0.0002 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-09-12.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…