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/getstream/agent-skills/stream-docsnpx skills add GetStream/agent-skills --skill stream-docsgit clone --depth 1 https://github.com/GetStream/agent-skillsWhat 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.00116 | $0.06589 |
| Opus 5 | $0.00058 | $0.03295 |
| Sonnet 5 | $0.00023 | $0.01318 |
| Haiku 4.5 | $0.00012 | $0.00659 |
Grade A, and why
stream-docs 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 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.
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 — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stream - Docs search (live SDK documentation)
Read first (every session): Glob
../stream/SKILL.mdand Read../stream/RULES.md(both ship with this skill) - RULES.md includes a Peer skills table for installing/invoking any other pack skills on demand.
Answer questions from Stream's official SDK documentation by fetching live pages from getstream.io. Covers Chat, Video, Activity Feeds, and Moderation across every framework and version.
Docs index: https://getstream.io/cli/llms.txt
No CLI gate, no up-front shell. This skill never invokes Write, Edit, npm, scaffold tools, or
Bash(getstream *). Pure docs questions with an explicit SDK reachWebFetchwithout running any shell command. A small read-only probe runs only on demand - inside Step 1a below - when the SDK can't be resolved from the user's input. If the user's question requires running the CLI or building code, offer to switch - the user re-enters via thestreamrouter or thestream-builderskill.
Honesty rules (read before anything else)
These rules are non-negotiable. Read them before every response.
-
Announce inference only when it happened. If you picked an SDK/version from anything other than explicit user input, say so in the first sentence - but only on the turn the inference happened:
- "Looking in Chat React v13 (detected from your package.json)..."
- "Inferring Video from your question about 'calls' - let me know if you meant something else..."
On follow-ups within the same SDK, stay silent - the user knows what's loaded. Only re-announce when the SDK changes. For explicit input (e.g.
/stream Chat React v14), no preamble is needed - go straight to the answer. -
Write for humans, not for the skill. Users don't know (or care) how this skill works - they want their answer. No internal workflow terminology, status narration, or process commentary should ever appear in output. The answer itself proves the fetch worked.
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 · 478 lines · 116 tokens per session scan A 3d2ec79256d4
stream-docs is a skill published in the GitHub repository GetStream/agent-skills (18 stars, last pushed 4d ago), licensed Apache-2.0. It adds 116 tokens to every session and 6,589 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
wukongim-cloud-analysis
Diagnose one exact live WuKongIM cloud Simulation Run or chat-lifecycle Cloud Lease through the repository Analysis MCP. Use when the user or a local Analysis Session asks Codex to inspect a run's cluster state, Prometheus signals, application logs, diagnostics, Controller task audits, profiles, or redacted config…
wukongim-chat-lifecycle
Operate the Codex-owned WuKongIM chat-lifecycle laboratory directly from the local repository. Use when the operator explicitly asks to buy temporary Alibaba Cloud servers and start the repair stability run, deploy a committed candidate to the same Lease, start or monitor the bounded long workload, diagnose a stopped…
wukongim-ops
Diagnose WuKongIM single-node or multi-node clusters through the embedded read-only Operations MCP. Use when investigating cluster health, nodes, physical Slots, exact channel runtime state, Controller tasks, fixed Prometheus signals, raw application logs, diagnostics, redacted config, backups, or bounded pprof…
compare
Multi-model code review. Fan out a bug or task to multiple LLMs, diff their findings, optionally debate, then dispatch subagents to fix in parallel. Use when the user types /compare or asks to compare models on a code issue.
activity-record
Query and orchestrate Arkloop Activity Record local activity data. Covers browser history, search terms, screen time, bluetooth, shell commands, window focus, keyboard, mouse, clipboard, screen content (accessibility tree), microphone audio transcription, and Codex sessions.
geogebra-drawing
GeoGebra 交互式数学可视化 Skill。生成 GGBScript 代码块，支持函数绘图、几何作图、坐标系构建和动态交互。.