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/GetStream/agent-skillsnpx agentmods add skills/getstream/agent-skills/stream-reactWrote 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/getstream/agent-skills/stream-react)<a href="https://agentmods.dev/skills/getstream/agent-skills/stream-react"><img src="https://agentmods.dev/badge/skills/getstream/agent-skills/stream-react/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/getstream/agent-skills/stream-react"><img src="https://agentmods.dev/badge/skills/getstream/agent-skills/stream-react.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.00268 | $0.07032 |
| Opus 5.5 | $0.00107 | $0.02813 |
| Sonnet 5.5 | $0.00054 | $0.01406 |
| Haiku 4.5 | $0.00027 | $0.00703 |
Grade B, and why
stream-react scanned grade B 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 26d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Bash(mv .scaffold*), Bash(rm -rf .scaffold), Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stream React (web) - scaffold + enhance + audit + migrate
Read first (every session): Read
RULES.md(React/Next.js non-negotiables) and the cross-cutting../stream/RULES.md. Where the two files state the same rule differently (e.g. Strict mode protection, Package manager), this pack'sRULES.mdwins for React work. Glob../stream/SKILL.md; if empty, install withgetstream skills stream.CLI: CLI usage (onboarding, credentials, auth, every
getstream apicall) lives in the root skill - its "Stream CLI" section in../stream/SKILL.md, with CLI safety in../stream/RULES.md. Glob../stream/SKILL.md; install silently if missing (getstream skills stream).
This skill builds, enhances, audits, and migrates Stream Chat, Video, and Feeds in React / Next.js web apps - the default pack for all web React work. It covers five tracks:
- Track A - Scaffold a new app: Steps 0-7 below. Use when the cwd is empty / new and the user said "build me a ... app".
- Track E - Enhance an existing app: see
enhance.md. Skips scaffold + theme; reuses the same SDK wiring and component blueprints. - Track F - Audit an existing integration (read-only): for "audit/review my video integration", "check my app against best practices", "is my video app production-ready?", "what am I missing before launch?". Video only: load the Integration best-practices audit section in
references/VIDEO.mdand follow its protocol - it has a Video-specific checklist + output contract. If the user asks to audit Chat or Feeds, say up front there is no dedicated best-practices checklist for those yet, then do a general docs-based review (fetch the relevant pages fromreferences/docs-map.mdand check the app against them) rather than applying the Video checklist. Skip onboarding, auth, the CLI, and all build steps - this track only reads the app and reports findings. Fix issues only if the user then asks. - Track M - Migrate / upgrade an SDK version: see
migrate.md. For "upgrade stream-chat-react to v14", "migrate to the new SDK", "bump my Stream version". Docs-driven: detect the installed version, fetch the matching release guide, apply it. Never migrate from memory. - Track S - Migrate from Sendbird: see
sendbird-migration.md. For "migrate my app from Sendbird to Stream", "replace @sendbird/uikit-react with Stream", "we're switching off Sendbird". Detects the existing Sendbird integration shape, swaps packages + init, re-implements each touchpoint (UI composition, channels, messages, events/pagination, moderation, theming) against the grounded Sendbird<->Stream mapping the file carries, then offers the separate data migration.
What ships with it
22 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.
- ai-integration.md 7.7 KB
- builder-ui.md 12 KB
- builder.md 7.4 KB
- enhance.md 8.4 KB
- migrate.md 4.9 KB
- references/CHAT-blueprints.md 8.3 KB
- references/CHAT.md 11 KB
- references/CROSS-PRODUCT.md 8.8 KB
- references/custom-ui.md 23 KB
- references/design-matching.md 79 KB
- references/docs-map.md 21 KB
- references/FEEDS-blueprints.md 17 KB
- references/FEEDS.md 23 KB
- references/MODERATION-blueprints.md 9.5 KB
- references/MODERATION.md 3.2 KB
- references/sendbird-mapping-extended.md 136 KB
- references/sendbird-mapping.md 34 KB
- references/VIDEO-blueprints.md 5.2 KB
- references/VIDEO.md 24 KB
- RULES.md 14 KB
- sdk.md 4.5 KB
- sendbird-migration.md 29 KB
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.
- 26d ago Changed · +2 lines · -7 tokens per session 9269cca1e1d1
- 1mo ago First seen · 274 lines · 275 tokens per session scan B 721a55d7911c
stream-react is a skill published in the GitHub repository GetStream/agent-skills (20 stars, last pushed today), licensed Apache-2.0. It adds 268 tokens to every session and 7,032 once invoked, about $0.0011 per session on Opus 5.5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
langbot-dev
Develop, build, and debug the LangBot core backend and web frontend. Use when working inside the LangBot repository — backend (Python/Quart, src/langbot/pkg), the Vite/React web UI, HTTP API controllers/services, Alembic migrations, or the MCP server. Covers the dev environment (uv, pnpm), repo layout, the API auth…
building-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
use-dom
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
frontend-design
Guidance for distinctive, intentional visual design when building or reshaping UI, HTML/React artifacts, dashboards, charts, and visual reports. Use before implementation to choose a content-specific structure, typography, and visual system that does not read as a templated default.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.