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.
git clone --depth 1 https://github.com/chambear2809/splunk-cisco-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/commands/chambear2809/splunk-cisco-skills/splunk-enterprise-public-exposure-hardening)<a href="https://agentmods.dev/commands/chambear2809/splunk-cisco-skills/splunk-enterprise-public-exposure-hardening"><img src="https://agentmods.dev/badge/commands/chambear2809/splunk-cisco-skills/splunk-enterprise-public-exposure-hardening/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/commands/chambear2809/splunk-cisco-skills/splunk-enterprise-public-exposure-hardening"><img src="https://agentmods.dev/badge/commands/chambear2809/splunk-cisco-skills/splunk-enterprise-public-exposure-hardening.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.00000 | $0.00225 |
| Opus 5.5 | $0.00000 | $0.00090 |
| Sonnet 5.5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
splunk-enterprise-public-exposure-hardening 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.
What it actually says
Render, preflight, apply, and validate hardening of an on-prem Splunk Enterprise deployment for public-internet exposure across all four edge surfaces (Splunk Web 8000, HEC 8088, S2S 9997, splunkd 8089) plus reference reverse-proxy / WAF / firewall templates and a structured operator handoff. Refuses to apply without --accept-public-exposure; refuses to apply below the SVD floor (10.2.2 / 10.0.5 / 9.4.10 / 9.3.11).
Read and follow the instructions in skills/splunk-enterprise-public-exposure-hardening/SKILL.md to help the user. If more detail is needed, also read skills/splunk-enterprise-public-exposure-hardening/reference.md.
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 · 6 lines · 0 tokens per session scan A 243e4594304e
splunk-enterprise-public-exposure-hardening is a command published in the GitHub repository chambear2809/splunk-cisco-skills (40 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 225 tokens. 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-03.
Other commands, from other repositories
cost-optimize
Reduce cloud costs across AWS, Azure, and GCP through rightsizing, reserved and spot capacity, storage tuning, and cost monitoring.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
scan
Scan AWS account for cost optimization.
migration
Generate Prisma database migration.