Borrowing it
Nothing to install: this file belongs to prantikmedhi/ClawNexus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/prantikmedhi/ClawNexus/main/AGENTS.mdgit clone --depth 1 https://github.com/prantikmedhi/ClawNexusWrote 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/instructions/prantikmedhi/clawnexus/agents-md)<a href="https://agentmods.dev/instructions/prantikmedhi/clawnexus/agents-md"><img src="https://agentmods.dev/badge/instructions/prantikmedhi/clawnexus/agents-md.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.02442 | $0.02442 |
| Opus 5 | $0.01221 | $0.01221 |
| Sonnet 5 | $0.00488 | $0.00488 |
| Haiku 4.5 | $0.00244 | $0.00244 |
Grade A, and why
ClawNexus AGENTS.md 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 8d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawNexus Office — AI Agent Development Guide
Created and maintained by Prantik Medhi
Overview
This document provides comprehensive development context and standards for developers working on ClawNexus Office. It covers project architecture, coding standards, integration patterns, and best practices for maintaining this multi-agent visualization platform.
Project Overview
ClawNexus Office is the professional visual monitoring and management frontend for the OpenClaw Multi-Agent system. It connects to the OpenClaw Gateway via WebSocket to visualize AI agent collaboration as a digital office and provides comprehensive console management interfaces.
Tech Stack
| Category | Technology |
|---|---|
| Language | TypeScript (ESM, strict mode) |
| UI Framework | React 19 |
| Build Tool | Vite 6 |
| State Management | Zustand 5 + Immer |
| Styling | Tailwind CSS 4 |
| 2D Rendering | SVG + CSS Animations |
| 3D Rendering | React Three Fiber (R3F) + @react-three/drei |
| Routing | React Router 7 |
| Charts | Recharts |
| i18n | i18next + react-i18next |
| Testing | Vitest + @testing-library/react |
| Real-time | Native WebSocket API |
Feature Modules
Office View (/)
Isometric-style 2D/3D virtual office for real-time AI agent status visualization:
- 2D Floor Plan — SVG office scene with desks, furniture (desk/chair/sofa/plant/coffee cup), Agent avatars, and status animations
- 3D Scene — R3F-rendered 3D office with character models, skill holograms, spawn portal effects
- Agent Avatars — Deterministically generated SVG avatars from agentId with status indicators (idle/working/speaking/error)
- Collaboration Lines — Visual connections for inter-Agent messaging
- Bubble Panels — Markdown text stream and tool call display
- Side Panels — Agent details, metrics charts (Token line chart/cost pie chart/activity heatmap), SubAgent graphs, event timeline
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.
- 8d ago First seen · 245 lines · 2,442 tokens per session scan A c65975111fa5
ClawNexus AGENTS.md is an instructions file published in the GitHub repository prantikmedhi/ClawNexus (5 stars, last pushed 3mo ago), licensed MIT. It adds 2,442 tokens to every session, about $0.0122 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-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.