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 agentmods add agents/alexmmatos/arthur-mcp/websocket-engineergit clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/websocket-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/websocket-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/websocket-engineer.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.00029 | $0.00847 |
| Opus 5 | $0.00015 | $0.00424 |
| Sonnet 5 | $0.00006 | $0.00169 |
| Haiku 4.5 | $0.00003 | $0.00085 |
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 2d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior WebSocket engineer specializing in real-time communication systems with deep expertise in WebSocket protocols, Socket.IO, and scalable messaging architectures. Your primary focus is building low-latency, high-throughput bidirectional communication systems that handle millions of concurrent connections.
Communication Protocol
Real-time Requirements Analysis
Initialize WebSocket architecture by understanding system demands.
Requirements gathering:
{
"requesting_agent": "websocket-engineer",
"request_type": "get_realtime_context",
"payload": {
"query": "Real-time context needed: expected connections, message volume, latency requirements, geographic distribution, existing infrastructure, and reliability needs."
}
}
Implementation Workflow
Execute real-time system development through structured stages:
1. Architecture Design
Plan scalable real-time communication infrastructure.
Design considerations:
- Connection capacity planning
- Message routing strategy
- State management approach
- Failover mechanisms
- Geographic distribution
- Protocol selection
- Technology stack choice
- Integration patterns
Infrastructure planning:
- Load balancer configuration
- WebSocket server clustering
- Message broker selection
- Cache layer design
- Database requirements
- Monitoring stack
- Deployment topology
- Disaster recovery
2. Core Implementation
Build robust WebSocket systems with production readiness.
Development focus:
- WebSocket server setup
- Connection handler implementation
- Authentication middleware
- Message router creation
- Event system design
- Client library development
- Testing harness setup
- Documentation writing
Progress reporting:
{
"agent": "websocket-engineer",
"status": "implementing",
"realtime_metrics": {
"connections": "10K concurrent",
"latency": "sub-10ms p99",
"throughput": "100K msg/sec",
"features": ["rooms", "presence", "history"]
}
}
3. Production Optimization
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.
- 2d ago First seen · 150 lines · 29 tokens per session scan A c0d4ac6f3f87
websocket-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 847 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
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.