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 xuiltul/animaworks --skill zoom-meeting-scribegit clone --depth 1 https://github.com/xuiltul/animaworksWrote 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/xuiltul/animaworks/zoom-meeting-scribe)<a href="https://agentmods.dev/skills/xuiltul/animaworks/zoom-meeting-scribe"><img src="https://agentmods.dev/badge/skills/xuiltul/animaworks/zoom-meeting-scribe/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/xuiltul/animaworks/zoom-meeting-scribe"><img src="https://agentmods.dev/badge/skills/xuiltul/animaworks/zoom-meeting-scribe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 74 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00078 | $0.01214 |
| Opus 5.5 | $0.00031 | $0.00486 |
| Sonnet 5.5 | $0.00016 | $0.00243 |
| Haiku 4.5 | $0.00008 | $0.00121 |
Grade A, and why
zoom-meeting-scribe 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 27d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Zoom Meeting Scribe (Listening, Summarizing, and Report with Approval)
The Zoom RTMS gateway injects meeting transcripts into your inbox as chunks every few minutes. Your role is to understand and organize the content as a listener-only participant, compile a report after the meeting ends, and post it only after receiving human approval.
Format of Incoming Messages
| Type | Header | Meaning |
|---|---|---|
| Live chunk | [Zoom会議実況 チャンク#N | 会議: {題名} ({会議ID}) | {開始時刻}〜] |
Speech during the meeting (followed by lines of speaker name: statement) |
| End notification | [Zoom会議終了 | 会議: {題名} ({会議ID}) | 全Nチャンク配信済み] |
Meeting ended. Signal to create a report |
- Chunks from the same meeting arrive in the same thread (
zoom-{会議UUID}) - If
[接続断により一部欠落]appears at the start of a chunk, the immediately preceding speech may be lost. Note the possibility of missing content in the report - Speaker names are Zoom display names. "Unknown" indicates speech where the speaker could not be identified
Workflow
1. On Receiving a Live Chunk — Stay Silent and Take It In
- Read the content and organize it sequentially in your own notes (working memory or notes):
- Decisions (who decided what)
- Action items (owner and deadline)
- Open issues and carry-over items
- Key points of the meeting flow
- Do not reply, post to channels, or intervene in the meeting in any way. You are the listener
- If you notice a missing chunk number, treat it as a gap in the transcript
2. Immediate Escalation of Urgent Matters (Exception)
Even during the meeting, if you detect any of the following, report the key points at that moment to your supervisor (the supervisor shown in your organization context) via send_message:
- Reports of outages, incidents, or security issues
- Decisions or requests with a deadline of today or the next business day
- Explicit action requests addressed to you or your team
- Mentions of significant legal or financial risks
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.
- 27d ago Changed · -1 lines · -7 tokens per session 09a7a084fcca
- 29d ago Changed e70ff0b82ac3
- 1mo ago First seen · 116 lines · 85 tokens per session scan A 3a011d6e53d2
zoom-meeting-scribe is a skill published in the GitHub repository xuiltul/animaworks (268 stars, last pushed 2d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,214 once invoked, about $0.0003 per session on Opus 5.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-08-30.
Other skills, from other repositories
efficient-execution
Reduce token waste and task completion time by choosing the simplest tool for each job.
Loop
Run the same task on a recurring cron schedule. Parses interval syntax (5m, 2h, 1d, "/15 "), records the schedule, and acknowledges back to the user.
local-document-organizer
Preview-first local file organizer. Scan a user-named folder, classify files with readable rules, show a plan, execute approved moves and undo them. Use for sorting Downloads, renaming into category folders, or reviewing organization history, including scoped metadata-only course persistence. Do not use for knowledge…
customer-email-assist
Review Gmail customer-support threads with a minimal-token, connector-first workflow. Use when Codex needs to read Gmail through the Codex Gmail connector, import cleaned messages into a local SQLite issue queue, apply deterministic cleanup and classification first, reserve model usage for JSON-only message…
Batch Run
Apply the same prompt or operation to a list of items in turn, collecting results. Useful for "do X to each of these files / PRs / records" tasks.
personal-workflow-automation
Define, preview, execute and inspect manually triggered workflows with ordered deterministic tool steps and approval gates. Use for repeatable multi-step course routines and explicit retries. Do not use for file classification, knowledge synthesis, background scheduling or replacing another skill's work.