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 chambear2809/splunk-cisco-skills --skill cisco-secure-email-web-gateway-setupgit 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/skills/chambear2809/splunk-cisco-skills/cisco-secure-email-web-gateway-setup)<a href="https://agentmods.dev/skills/chambear2809/splunk-cisco-skills/cisco-secure-email-web-gateway-setup"><img src="https://agentmods.dev/badge/skills/chambear2809/splunk-cisco-skills/cisco-secure-email-web-gateway-setup/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/chambear2809/splunk-cisco-skills/cisco-secure-email-web-gateway-setup"><img src="https://agentmods.dev/badge/skills/chambear2809/splunk-cisco-skills/cisco-secure-email-web-gateway-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.01299 |
| Opus 5 | $0.00015 | $0.00649 |
| Sonnet 5 | $0.00006 | $0.00260 |
| Haiku 4.5 | $0.00003 | $0.00130 |
Grade A, and why
cisco-secure-email-web-gateway-setup 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 8d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cisco Secure Email/Web Gateway Setup
Prerequisites
| Tool or access | Purpose | Verify |
|---|---|---|
| Bash | Render package, index, macro, and transport assets | bash --version |
| Splunk administrative access | Install ESA/WSA add-ons and run searches | Confirm target-tier access |
| SC4S or file-monitor owner | Deliver ESA/WSA events to the parsing tier | Confirm one transport owner per source |
Workflow Overview
┌───────────┐ ┌─────────────────┐ ┌──────────────────┐ ┌───────────────┐
│ Preflight │ → │ Render packages │ → │ Configure ingest │ → │ Validate data │
└───────────┘ └─────────────────┘ └──────────────────┘ └───────────────┘
When to Activate
- Onboard Cisco Email Security Appliance (ESA) or Web Security Appliance (WSA) logs.
- Configure email/netproxy indexes, macros, parser placement, or transport ownership.
- Diagnose missing source types, CIM fields, or dashboard evidence.
Scope
This skill renders and validates Splunk-side ESA/WSA onboarding. It does not configure appliance policy or silently create competing syslog and file-monitor paths. Select one transport owner and preserve parser placement.
Examples
Render both product paths for SC4S ownership:
bash skills/cisco-secure-email-web-gateway-setup/scripts/render_ingestion_assets.sh \
--product both
Expected output: reviewable package, index, macro, parser, transport, and validation assets are written without changing an appliance.
Run strict validation after events arrive:
bash skills/cisco-secure-email-web-gateway-setup/scripts/validate.sh \
--completion --product both
Expected output: ESA and WSA package, source type, event, CIM, and dashboard
handoff checks report [PASS] or exit nonzero.
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Events are duplicated | SC4S and file monitoring both collect the source | Keep one transport owner |
| Fields are missing | Parsing add-on is placed on the wrong tier | Correct parser placement and retest new events |
| Wrong dashboard index | Macros differ from inputs | Align macros with the index plan |
| One product passes | Only ESA or WSA transport is active | Validate each selected product independently |
What ships with it
6 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.
- 8d ago First seen · 147 lines · 30 tokens per session scan A b139fd3e2a3f
cisco-secure-email-web-gateway-setup is a skill published in the GitHub repository chambear2809/splunk-cisco-skills (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 1,299 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-09-03.
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…