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 easyzoom/aix-skills --skill zoom-shell-integrationgit clone --depth 1 https://github.com/easyzoom/aix-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/easyzoom/aix-skills/zoom-shell-integration)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/zoom-shell-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/zoom-shell-integration/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/easyzoom/aix-skills/zoom-shell-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/zoom-shell-integration.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.00034 | $0.00621 |
| Opus 5 | $0.00017 | $0.00311 |
| Sonnet 5 | $0.00007 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
zoom-shell-integration 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zoom-shell Integration
Overview
Use this skill when the user explicitly means an embedded zoom-shell style MCU command console. Because the name is ambiguous, first confirm this is an embedded shell library, not the Zoom desktop application or a security research reverse shell.
When To Use
Use this skill when:
- The user mentions
zoom-shellin the context of MCU firmware, serial CLI, UART shell, or embedded command parsing. - A tiny shell has missing commands, broken argument parsing, blocking output, or unreliable serial input.
- The task involves command tables, help output, bounded buffers, terminal line endings, or production debug command guards.
Do not use this skill for Zoom meeting apps, desktop automation, reverse shells, or non-embedded security research.
First Questions
Ask for:
- The exact
zoom-shellrepository or source package. - Target MCU, compiler, RTOS/bare-metal runtime, and serial transport.
- Input model: polling, interrupt RX, DMA RX, RTOS queue, USB CDC, RTT, or TCP.
- Command registration method and current command list.
- Maximum command length, argument count, and stack/RAM limits.
- Whether shell commands are allowed in production firmware.
Integration Checklist
-
Confirm the library identity. Verify the user-provided source is an embedded shell and not an unrelated Zoom project.
-
Prove raw transport. Check RX/TX before debugging shell parsing.
-
Configure bounded buffers. Command line, argument list, history, and output buffers must fit RAM and reject overflow.
-
Register one read-only command. Start with
help,version, orstatus. -
Validate argument parsing. Test missing arguments, extra arguments, invalid numbers, and long input.
-
Guard dangerous commands. Reset, erase, format, firmware update, calibration, and production-data commands need build guards or explicit authorization.
Common Failures
- Wrong library selected because
zoom-shellname was ambiguous. - Shell receives characters but parser is not pumped from the main loop or task.
- Newline/backspace handling mismatches terminal settings.
- Command buffers overflow on pasted input.
- Debug commands remain enabled in release builds.
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 · 82 lines · 34 tokens per session scan A aff202b7ba7e
zoom-shell-integration is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 621 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
container-home
Answer questions, assist with planning, and help with design decisions for Mick's off-grid shipping container lake home project. Trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.