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 instructions/emberagi/arbitrum-vibekit/claude-mdgit clone --depth 1 https://github.com/EmberAGI/arbitrum-vibekitWrote 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/emberagi/arbitrum-vibekit/claude-md)<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="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.03059 | $0.03059 |
| Opus 5 | $0.01529 | $0.01529 |
| Sonnet 5 | $0.00612 | $0.00612 |
| Haiku 4.5 | $0.00306 | $0.00306 |
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 5d 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 — 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 addorpnpm add -Dto ensure latest versions - Never manually edit
package.jsondependencies - 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
tsxfor 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.mdand 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.mdFIRST 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.mdFIRST for implementation patterns
Environment Configuration
- Copy
.env.exampleto.envfor 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
dotenvpackage- Node.js 20.6+ supports native
.envfile loading via the--env-fileflag - Integration and e2e test scripts use
tsx --env-file=.env.testto load test environment variables - See
package.jsonscripts:test:int,test:e2e, andtest:record-mocks - No need to manually call
dotenv/configor importdotenv
- Node.js 20.6+ supports native
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.
- 5d ago First seen · 348 lines · 3,059 tokens per session scan A b41ea773e42d
arbitrum-vibekit CLAUDE.md is an instructions file published in the GitHub repository EmberAGI/arbitrum-vibekit (53 stars, last pushed 27d ago), licensed MIT. It adds 3,059 tokens to every session, about $0.0153 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
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).
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.
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.
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.
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).