What is arbitrum-vibekit CLAUDE.md?

A development and testing guide for a TypeScript project using pnpm, Node.js-style modules, and Vitest. It also defines Test-Driven Development, an approach where tests are written before or alongside the code they check, and gives rules for test mocks and utilities.

Use it when changing TypeScript code, test infrastructure, mock handlers, test utilities, or tests that follow the project’s TDD process.

It keeps dependency changes, tests, and mock network behavior consistent, reducing errors caused by using the wrong package manager or outdated test patterns.

How EmberAGI/arbitrum-vibekit configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to EmberAGI/arbitrum-vibekit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/EmberAGI/arbitrum-vibekit/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/EmberAGI/arbitrum-vibekit

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/emberagi/arbitrum-vibekit/claude-md/github.svg)](https://agentmods.dev/instructions/emberagi/arbitrum-vibekit/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/emberagi/arbitrum-vibekit/claude-md"><img src="https://agentmods.dev/badge/instructions/emberagi/arbitrum-vibekit/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/emberagi/arbitrum-vibekit/claude-md"><img src="https://agentmods.dev/badge/instructions/emberagi/arbitrum-vibekit/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3,059 This file is loaded in full into every session.

When invoked 3,059 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.03059	$0.03059
Opus 5.5	$0.01224	$0.01224
Sonnet 5.5	$0.00612	$0.00612
Haiku 4.5	$0.00306	$0.00306

Measured 2mo ago against content hash b41ea773e42d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

arbitrum-vibekit CLAUDE.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 2mo 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.

CLAUDE.md · 348 lines

How it starts

The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Please also reference the following documents as needed:

@.claude/memories/msw-handlers.md description: "MSW handler rules for integration test fidelity" globs: "/tests/mocks//*"

Development Guidelines

Package Management

ALWAYS use pnpm - never use npm
Install dependencies with pnpm add or pnpm add -D to ensure latest versions
Never manually edit package.json dependencies - use pnpm commands
For CI/CD, use non-interactive flags: pnpm install --frozen-lockfile

TypeScript Configuration

Target: ES2022 with NodeNext module resolution
Strict mode enabled
Source maps for debugging
Use tsx for development execution (already configured in dev scripts)

Testing Approach

Unit tests mirror source directory structure
Use Vitest for testing framework (migrating from Mocha)
Follow Test-Driven Development (TDD) practices
For detailed testing guidelines, see docs/testing-strategy.md and the TDD agents

Working with Test Infrastructure and Code

When modifying test infrastructure (MSW handlers, test utilities, mock data):

ALWAYS read .claude/agents/tdd-test-writer.md FIRST for requirements and patterns
This includes creating new handlers, updating existing ones, or adding mock utilities

When implementing or modifying code (whether making tests pass or any other changes):

ALWAYS read .claude/agents/test-driven-coder.md FIRST for implementation patterns

Environment Configuration

Copy .env.example to .env for local development
Required: API keys for providers (Dune, Birdeye, etc.)
Chain configurations in environment variables
Node.js native environment variable loading - we do NOT use the dotenv package
- Node.js 20.6+ supports native .env file loading via the --env-file flag
- Integration and e2e test scripts use tsx --env-file=.env.test to load test environment variables
- See package.json scripts: test:int, test:e2e, and test:record-mocks
- No need to manually call dotenv/config or import dotenv

Read the full file on GitHub · 348 lines

Changes

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.

2mo ago First seen · 348 lines · 3,059 tokens per session scan A b41ea773e42d

Subscribe to this mod's changes

arbitrum-vibekit CLAUDE.md is an instructions file published in the GitHub repository EmberAGI/arbitrum-vibekit (53 stars, last pushed 3mo ago), licensed MIT. It adds 3,059 tokens to every session, about $0.0122 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.

arbitrum-vibekit CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
arbitrum-vibekit CLAUDE.mdEmberAGI/arbitrum-vibekit	Instructions file	53	3mo ago	MIT	A	3,059	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode ai-customization.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	1,907	GitHub Copilot

arbitrum-vibekit: Instructions file for Claude Code