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.
git clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/websocket-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/websocket-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/websocket-expert.svg" alt="Measured on agentmods" 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.00028 | $0.00423 |
| Opus 5 | $0.00014 | $0.00211 |
| Sonnet 5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
websocket-expert 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 3d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- WebSocket protocol RFC 6455 compliance
- Secure WebSocket (WSS) implementation
- Creating and maintaining WebSocket connections
- Handling message framing and parsing
- Binary and text data transmission
- Connection lifecycle management
- Managing multiple concurrent WebSocket connections
- WebSocket handshake process
- Network error handling and reconnection strategies
- Implementing client and server-side WebSockets
Approach
- Establish secure WebSocket connections with TLS
- Implement efficient message passing with WebSockets
- Optimize WebSocket server performance for scalability
- Monitor and log WebSocket traffic for debugging
- Secure WebSocket applications against common vulnerabilities
- Handle WebSocket disconnections gracefully
- Validate WebSocket frames according to protocol
- Use subprotocols for specific application needs
- Ensure compatibility with major browser WebSocket APIs
- Test WebSocket connections under varying network conditions
Quality Checklist
- Validate WebSocket URLs for security and correctness
- Ensure WebSocket handshake follows proper protocol sequence
- Implement appropriate error messages for failed connections
- Test WebSocket message size limits and fragmentation
- Ensure WebSocket server can handle high connection churn
- Monitor WebSocket connection uptime and reconnection attempts
- Validate server and client support for WebSocket extensions
- Secure WebSocket sessions against injection attacks
- Conduct load testing for WebSocket application scalability
- Implement logging for all WebSocket interactions
Output
- RFC 6455-compliant WebSocket implementation
- Secure and encrypted WebSocket applications
- Scalable WebSocket server setups
- Optimized message delivery using WebSockets
- Robust error-handling and recovery strategies
- Real-time communication demos using WebSockets
- WebSocket session management and tracking tools
- Practical examples of WebSocket client-server interactions
- Performance metrics for WebSocket server environments
- Detailed documentation of WebSocket implementation
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.
- 3d ago First seen · 55 lines · 28 tokens per session scan A 512a7aaece09
websocket-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 28 tokens to every session and 423 once invoked, about $0.0001 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-03.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…