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 cometchat/cometchat-skills --skill cometchat-angular-v5-testinggit clone --depth 1 https://github.com/cometchat/cometchat-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/cometchat/cometchat-skills/cometchat-angular-v5-testing)<a href="https://agentmods.dev/skills/cometchat/cometchat-skills/cometchat-angular-v5-testing"><img src="https://agentmods.dev/badge/skills/cometchat/cometchat-skills/cometchat-angular-v5-testing/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-angular-v5-testing"><img src="https://agentmods.dev/badge/skills/cometchat/cometchat-skills/cometchat-angular-v5-testing.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.00088 | $0.01517 |
| Opus 5 | $0.00044 | $0.00758 |
| Sonnet 5 | $0.00018 | $0.00303 |
| Haiku 4.5 | $0.00009 | $0.00152 |
Grade A, and why
cometchat-angular-v5-testing 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 yesterday.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ground truth:
@cometchat/chat-uikit-angular@5(5.1.0–5.2.0 verified). The Angular UI Kit docs have no testing page — the strategy here is the pack's own, and is labelled as such rather than presented as documented (a tracked DOCS GAP). Any kit symbol a test mocks must still exist in theangular-v5catalog, and its real shape comes from the component's.mdtwin viacometchat-angular-v5-core/references/docs-map.md— mock the API the kit actually exposes, never one invented to fit the test.
Companion skills (read first)
cometchat-angular-v5-core— init/login lifecycle, which is what makes tests hang if unmocked.
Use this skill when
Writing tests for a component that renders kit components, or diagnosing tests that hang or fail on network.
Decide what you are testing
| Testing | Approach |
|---|---|
| Your logic — selection, routing, state | Unit test with CometChat mocked |
| Kit component internals | Don't. It is a third-party dependency with its own tests |
| Your app's chat flow end-to-end | Playwright against a real dev app, two accounts |
| Realtime delivery | Manual, two browsers. Not automatable cheaply |
The common mistake is unit-testing kit internals. Test the seam: given a click, does your component set the right active chat?
Mock CometChat in unit tests
Kit components open sockets and call the API at construction. Left real, tests hang, fail offline, and pollute a live app with test data.
// src/testing/cometchat.mock.ts
export const cometChatUIKitMock = {
initFromSettings: jest.fn().mockResolvedValue({}),
login: jest.fn().mockResolvedValue({ getUid: () => 'test-uid' }),
loginWithAuthToken: jest.fn().mockResolvedValue({ getUid: () => 'test-uid' }),
logout: jest.fn().mockResolvedValue(undefined),
getLoggedInUser: jest.fn().mockReturnValue({ getUid: () => 'test-uid' }),
isInitialized: jest.fn().mockReturnValue(true),
isCallingEnabled: jest.fn().mockReturnValue(false),
};
Point the module at it (Jest):
jest.mock('@cometchat/chat-uikit-angular', () => ({
...jest.requireActual('@cometchat/chat-uikit-angular'),
CometChatUIKit: cometChatUIKitMock,
}));
Keep requireActual so real component classes and ChatStateService still exist — you want your own wiring exercised, only the network faked.
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.
- yesterday First seen · 113 lines · 88 tokens per session scan A 1cf7458a18cf
cometchat-angular-v5-testing is a skill published in the GitHub repository cometchat/cometchat-skills (105 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 1,517 once invoked, about $0.0004 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-12.
Other skills, from other repositories
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
qa/test-strategy
A testing strategy based on the testing pyramid: many small unit tests, fewer integration tests, and a smaller set of end-to-end tests that follow real user journeys. It also defines checks for security, boundaries, permissions, and business consistency.
e2e-testing
AI-powered E2E testing for any app — Flutter, React Native, iOS, Android, Electron, Tauri, KMP, .NET MAUI. Connects via MCP to running apps so the agent can take screenshots, tap elements, enter text, scroll, inspect UI trees, and verify state with natural language. Use when the user wants to test an app's UI…