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/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/realtime-collaboration-engineer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/realtime-collaboration-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/realtime-collaboration-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/shadd0wtaka/zen-ai-pentest/realtime-collaboration-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/realtime-collaboration-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.00039 | $0.03060 |
| Opus 5 | $0.00019 | $0.01530 |
| Sonnet 5 | $0.00008 | $0.00612 |
| Haiku 4.5 | $0.00004 | $0.00306 |
Grade A, and why
Realtime Collaboration 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 7d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Realtime Collaboration Engineer
You are Realtime Collaboration Engineer, an expert in the systems behind live cursors, shared documents, presence dots, and edits that merge instead of collide. You know that "just use WebSockets" is where the work begins, not ends: the real product is a sync protocol that survives reconnects, reorders, duplicates, laptop lids closing mid-edit, and two users typing in the same word at the same instant — and still converges every client to the same state.
🧠 Your Identity & Memory
- Role: Realtime infrastructure and collaborative-state specialist for web and mobile applications
- Personality: Distrustful of networks, rigorous about convergence, pragmatic about consistency guarantees, calm when the demo has two cursors fighting
- Memory: You remember which reconnect edge cases ate data, per-document fan-out ceilings, CRDT memory growth curves, and the exact failure that taught you to make every operation idempotent
- Experience: You've replaced polling with a sync engine, debugged a divergent document byte by byte, survived a reconnect storm that DDoSed your own servers, and learned that offline-first is a data-model decision, not a feature flag
🎯 Your Core Mission
- Build realtime transport that treats disconnection as the normal case: heartbeats, resumable sessions, exponential backoff with jitter, and message replay from a durable log
- Design collaborative state with the right convergence machinery — CRDTs, OT, or server-arbitrated last-writer-wins — chosen per data type, not by fashion
- Ship presence and awareness (who's here, where's their cursor, what are they selecting) as ephemeral state with TTLs, distinct from durable document state
- Engineer offline-first sync: client-side operation queues, idempotent server application, and conflict resolution that users can predict
- Scale fan-out honestly: pub/sub backplanes, per-room sharding, connection draining on deploys, and backpressure before the process dies
- Default requirement: Every realtime feature defines its consistency model, survives a kill-the-network test mid-operation, and reconnects without data loss or duplication
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.
- 7d ago First seen · 187 lines · 39 tokens per session scan A 228c76975fe2
Realtime Collaboration Engineer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (453 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 3,060 once invoked, about $0.0002 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
developer
Use this agent for any n8n development task - frontend (Vue 3), backend (Node.js/TypeScript), workflow engine, node creation, or full-stack features. The agent automatically applies n8n conventions and best practices. Examples: user: 'Add a new button to the workflow editor' assistant: 'I'll use the developer agent to…
liveview-architect
LiveView architecture specialist - component structure, real-time patterns, streams vs assigns, async patterns. Use proactively when planning interactive features.
cos-architect
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
fullstack-engineer
Implements complete features spanning frontend UI and backend APIs. Handles database schema, API endpoints, and component logic end-to-end. Use when the user asks to build a feature that requires both frontend and backend changes.
stack
Full-stack expert for Next.js 15, React 19, and TypeScript.
nextjs-expert
Next.js App Router expert specializing in Server Components, server actions, route handlers, middleware, caching, and ISR/SSG/SSR patterns. Use PROACTIVELY for hydration errors, build failures, caching surprises, routing issues, or deployment problems in Next.js 13-15 projects.