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 agentmods add skills/jakeasmith/omada-controller-skill/omada-controllernpx skills add jakeasmith/omada-controller-skill --skill omada-controllergit clone --depth 1 https://github.com/jakeasmith/omada-controller-skillWhat 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 | $0.00076 | $0.02005 |
| Opus 5 | $0.00038 | $0.01002 |
| Sonnet 5 | $0.00015 | $0.00401 |
| Haiku 4.5 | $0.00008 | $0.00200 |
Grade B, and why
omada-controller scanned grade B with 2 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 2d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
The API wrapper script is at `scripts/omada-api.sh` relative to this skill's directory. On first use in a session, find the script path using Glob to search for `**/omada-controller/scripts/omada-api.sh`. Use the discove Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
compatibility: Requires curl and network access to an Omada SDN Controller. The controller must have Open API enabled with client credentials configured. How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Omada SDN Controller API
Manage TP-Link Omada SDN Controllers via the Open API (OpenAPI 3.0.1).
Compatibility
The Open API is available in Omada SDN Controller v5.9 and later (both the Software Controller and Cloud-Based Controller). Earlier versions only have an undocumented internal API that uses cookie-based session auth — this skill does not cover that legacy API.
The Open API feature must be explicitly enabled by an administrator before use.
Environment Setup
Before making any API calls, you need three environment variables. If the user has not provided these or a .env file does not exist, walk them through the setup:
-
Find the controller URL — Ask the user for their Omada Controller address. This is typically
https://<host>:8043for the Software Controller. The port may differ if customized during installation. -
Create API credentials — Guide the user to:
- Log into the Omada Controller web UI
- Navigate to Global View > Settings > Platform Integration > Open API
- Click Add New App
- Set the type to Client (not Gateway)
- Copy the generated Client ID and Client Secret
-
Create the
.envfile — Have the user create a.envfile in the project root:OMADA_URL=https://omada.example.com:8043 OMADA_CLIENT=your-client-id OMADA_SECRET=your-client-secret
Never commit .env to git. Ensure .gitignore includes it.
Load variables before making requests:
export $(grep -v '^#' .env | xargs)
Do NOT use source .env — variables won't propagate to subshells or curl.
If auth fails, common causes are:
- The Open API feature is not enabled on the controller
- The client app type is set to Gateway instead of Client
- The controller URL is wrong or missing the port
- The client secret was rotated in the UI but not updated in
.env
Locating the Wrapper Script
The API wrapper script is at scripts/omada-api.sh relative to this skill's directory. On first use in a session, find the script path using Glob to search for **/omada-controller/scripts/omada-api.sh. Use the discovered absolute path for all subsequent calls. For example, if the skill is installed at .claude/skills/omada-controller/, the script path is .claude/skills/omada-controller/scripts/omada-api.sh.
What ships with it
3 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.
- 2d ago First seen · 193 lines · 76 tokens per session scan B de60bbb5a789
omada-controller is a skill published in the GitHub repository jakeasmith/omada-controller-skill (5 stars, last pushed 5mo ago), licensed MIT. It adds 76 tokens to every session and 2,005 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (enumerates other installed skills, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.