Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/chambear2809/splunk-cisco-skillsnpx agentmods add skills/chambear2809/splunk-cisco-skills/cisco-webex-setupWrote 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-webex-setup)<a href="https://agentmods.dev/skills/chambear2809/splunk-cisco-skills/cisco-webex-setup"><img src="https://agentmods.dev/badge/skills/chambear2809/splunk-cisco-skills/cisco-webex-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-webex-setup"><img src="https://agentmods.dev/badge/skills/chambear2809/splunk-cisco-skills/cisco-webex-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 106 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.01554 |
| Opus 5 | $0.00015 | $0.00777 |
| Sonnet 5 | $0.00006 | $0.00311 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
cisco-webex-setup scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Bash, `curl`, and `jq` | Run setup and REST configuration helpers | `command -v bash curl jq` | How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cisco Webex Setup
Prerequisites
| Tool or access | Purpose | Verify |
|---|---|---|
Bash, curl, and jq |
Run setup and REST configuration helpers | command -v bash curl jq |
| Splunk administrative access | Install the add-on/app and configure inputs | Confirm search-tier REST access |
| Webex OAuth application | Authorize selected organizations and endpoints | Store client material in protected files |
Workflow Overview
┌───────────┐ ┌────────────────┐ ┌──────────────────┐ ┌────────────────────┐
│ Preflight │ → │ Install add-on │ → │ Configure inputs │ → │ Validate dashboards │
└───────────┘ └────────────────┘ └──────────────────┘ └────────────────────┘
When to Activate
- Onboard Webex Meetings, administrative audit, quality, or calling data.
- Configure generic Webex REST or Contact Center search inputs.
- Diagnose OAuth, index, source-type, macro, or dashboard failures.
Scope
This skill configures documented Webex collection and dashboard prerequisites. It does not create OAuth applications, expose tokens in chat, or enable every endpoint without reviewing scope, privacy, rate limits, and event volume.
Examples
Install the Webex add-on and companion app:
bash skills/cisco-webex-setup/scripts/setup.sh --install
Expected output: required packages and index/macro prerequisites are installed or a topology-specific manual handoff is emitted.
Run strict completion checks after configuring selected inputs:
bash skills/cisco-webex-setup/scripts/validate.sh --completion
Expected output: package, OAuth account, enabled input, event, macro, and
dashboard evidence report [PASS]; incomplete coverage exits nonzero.
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| OAuth returns 401/403 | Grant/scope is wrong | Correct app and credential files |
| API returns 429 | Input scope or interval exceeds rate limits | Reduce endpoints or increase polling intervals |
| One dataset is absent | Its dedicated input is disabled or unauthorized | Validate each selected input independently |
| Empty dashboards | Macro/source type is wrong | Validate events before dashboards |
What ships with it
7 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.
- 9d ago First seen · 183 lines · 30 tokens per session scan A 671478ab8b34
cisco-webex-setup is a skill published in the GitHub repository chambear2809/splunk-cisco-skills (37 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 1,554 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…
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…