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/cometchat/cometchat-skillsnpx agentmods add skills/cometchat/cometchat-skills/cometchat-react-v7-placementWrote 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/cometchat/cometchat-skills/cometchat-react-v7-placement)<a href="https://agentmods.dev/skills/cometchat/cometchat-skills/cometchat-react-v7-placement"><img src="https://agentmods.dev/badge/skills/cometchat/cometchat-skills/cometchat-react-v7-placement/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/cometchat/cometchat-skills/cometchat-react-v7-placement"><img src="https://agentmods.dev/badge/skills/cometchat/cometchat-skills/cometchat-react-v7-placement.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.00071 | $0.03033 |
| Opus 5.5 | $0.00028 | $0.01213 |
| Sonnet 5.5 | $0.00014 | $0.00607 |
| Haiku 4.5 | $0.00007 | $0.00303 |
Grade A, and why
cometchat-react-v7-placement 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 1mo 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ground truth:
@cometchat/chat-uikit-react@7. Uses only components defined incometchat-react-v7-core/-components(from live v7 docs). Status: catalog-verified vs installed 7.1.0 (exports-only web-v7.json). Fetch layout-specific props from the component's.mdtwin (../cometchat-react-v7-core/references/docs-map.md).
Companion skills (read first)
cometchat-react-v7-core— install,init→login→render, provider. This skill ASSUMES it.cometchat-react-v7-components— the component catalog this composes.
Use this skill when
Deciding/wiring WHERE chat lives — and either (a) growing the core surface into the whole combined chat app (selector tabs ↔ messages ↔ details/thread/search side panel + incoming call) when the user asks for the full app, or (b) a scoped-down sidebar/split, popup/floating widget, or embedded panel. Triggers: "build a full chat app", "add users/groups/calls tabs and a side panel", "add chat as a sidebar", "full screen chat page", "chat popup widget", "embed chat in my dashboard". Note: a plain unscoped "add chat" defaults to the production-ready CORE surface (list ↔ message pane) in cometchat-react-v7-core — grow to the combined app below only on request.
Prerequisites & install
Covered by core. No new package.
Placement patterns (BAKED) — each composes core components
- Core surface (THE DEFAULT for an unscoped "add chat") — production-ready, but lean. Inside
CometChatErrorBoundary→ ONECometChatProvider, a two-column layout: aCometChatConversationsLIST ↔ a MESSAGE pane (CometChatMessageHeader+CometChatMessageList+CometChatMessageComposer), sized per../cometchat-react-v7-core/references/layout.md, with the thread-replies panel and the in-chat scoped message search wired by DEFAULT (opt-out only) and the global conversation search bar wired-or-hidden, collapsing to one pane on mobile. One small host state object coordinates {selected conversation, which side view (thread | in-chat-search | none)}. Complete and wired — NOT a bare demo — but NOT the whole app. See the "Core-surface recipe" below. - Grow to the full combined app (on request) — the whole app the official sample ships. When the user asks for the full app, grow the core surface into a three-column layout, all under
CometChatErrorBoundary→ ONECometChatProvider: a SELECTOR column (the list for the active tab —CometChatConversations/CometChatUsers/CometChatGroups/CometChatCallLogs— + a tab bar), a MESSAGE pane, and a mutually-exclusive SIDE panel (user/group details, a threadCometChatThreadHeader+ list/composer, or a scopedCometChatSearch), plusCometChatIncomingCallmounted at root. One host state object coordinates {active tab, selected user/group, thread parent, which side panel}. It is the UNION of the core surface + these growths — see the "Combined-app recipe (grow target)" below. Least-code = reach for these drop-ins (HOW). - Sidebar / split: conversations list in a fixed side panel; the message pane fills the rest. Selection state links list → message pane. (Scoped-down variant.)
- Popup / floating widget: a toggle button mounts the chat panel in an overlay; keep
CometChatProvidermounted at app root so init/login persist across open/close. (Scoped-down variant.) - Embedded panel: drop the message components into an existing page region; reuse the host layout/containers. (Scoped-down variant.)
What ships with it
1 file 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.
- 1mo ago First seen · 107 lines · 71 tokens per session scan A e0407c98f0fa
cometchat-react-v7-placement is a skill published in the GitHub repository cometchat/cometchat-skills (155 stars, last pushed 10d ago), licensed MIT. It adds 71 tokens to every session and 3,033 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-09-12.
Other skills, from other repositories
extract-source-sample
Given the path to a finished content-goose ad-run folder, extract everything that defines that ad — recipe shot list, VO script, characters, voices, world, atom-skills, master mp4 — and emit a source-sample.json in the exact shape the upload-ad-sample skill writes to the Goose Ads library. Also links every character…
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
frontend
Builds, styles, and polishes anything drawn with HTML, CSS, or SVG: web UI, pages, components, HTML reports rendered to PDF or print, figures, PNG/SVG diagrams, slides, and images for Notion or Slack. Use for any styling, layout, animation, or visual-quality task, or when asked to make something look or feel a certain…
21st-ui
Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.
Error Boundary Tester
Validate error boundary implementations in React and other frameworks ensuring graceful degradation, proper fallback UI rendering, and error recovery flows.
shadcn
Current best-practices guide for shadcn/ui applications. Before applying primitive-specific guidance, inspect whether the checked-in components use Radix UI or Base UI; current shadcn supports both (Base UI is the default for new projects) and their composition APIs differ. Component installs and upgrades go through…