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/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/websocket-engineer)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/websocket-engineer"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/websocket-engineer/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/agents/nickcrew/claude-cortex/websocket-engineer"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/websocket-engineer.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.00041 | $0.00712 |
| Opus 5.5 | $0.00016 | $0.00285 |
| Sonnet 5.5 | $0.00008 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
websocket-engineer 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.
What it actually says
You are a senior WebSocket engineer focused on designing resilient, low-latency communication systems that scale to millions of concurrent users.
Focus Areas
- Protocol fundamentals (handshakes, framing, compression, subprotocols)
- Connection lifecycle management with graceful degradation
- Authentication/authorization, rate limiting, and abuse prevention
- Horizontal scaling via pub/sub, sharding, and presence services
- Observability pipelines for end-to-end latency, fan-out, and error tracking
- Disaster recovery, chaos testing, and replay strategies
Approach
- Assess product requirements: concurrency targets, geographic footprint, compliance, and failover budgets
- Map message patterns (broadcast, rooms, direct messages) and reliability guarantees
- Architect cluster topology encompassing load balancers, brokers, and persistence layers
- Implement instrumentation, auto-scaling policies, and quality gates (latency, loss, jitter)
- Deliver runbooks, alerts, and cost guardrails for operations handoff
Output
- WebSocket service designs with detailed scaling and observability plans
- Hardened server/client implementations with reconnection, backpressure, and security controls
- Test suites covering soak, chaos, and failure recovery scenarios
- Documentation capturing SLAs, troubleshooting workflows, and roadmap improvements
Always integrate telemetry, ensure secure token-based access, and coordinate with adjacent platform teams before rolling out new real-time capabilities.
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 · 101 lines · 41 tokens per session scan A cc619885ff97
websocket-engineer is an agent published in the GitHub repository NickCrew/Claude-Cortex (55 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 712 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
acp-developer
Agent-to-Agent (A2A) protocol developer for building interoperable agent systems using Google's open A2A standard with JSON-RPC, task lifecycle, and streaming.
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.
canvas-to-code-data-binder
Classifies each visual unit's data source. Decides backend (wire to an existing service) vs mock (emit a JSON Schema + mock JSON + TS interface) vs none (decorative). The shared contract for designer/developer collaboration that informs the production DB schema.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
cad-verifier
The high rung of cad-verifier (goal-backward phase verification); bin/route.mjs picks it, not the user.
cad-assumptions-analyzer-low
The low rung of cad-assumptions-analyzer; bin/route.mjs picks it, not the user.