Borrowing it
Nothing to install: this file belongs to dean0x/autobeat. 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/dean0x/autobeat/main/CLAUDE.mdgit clone --depth 1 https://github.com/dean0x/autobeatWrote 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/dean0x/autobeat/claude-md)<a href="https://agentmods.dev/instructions/dean0x/autobeat/claude-md"><img src="https://agentmods.dev/badge/instructions/dean0x/autobeat/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.05031 | $0.05031 |
| Opus 5 | $0.02516 | $0.02516 |
| Sonnet 5 | $0.01006 | $0.01006 |
| Haiku 4.5 | $0.00503 | $0.00503 |
Grade A, and why
autobeat 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 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides project-specific guidance for Claude Code when working on Autobeat.
Project Overview
Autobeat is an MCP (Model Context Protocol) server that enables task delegation to background Claude Code instances. It uses hybrid event-driven architecture with workers, task dependencies (DAG-based), and SQLite persistence.
Core Concept: Transform a dedicated server into an AI powerhouse - orchestrate multiple Claude Code instances through one main session for parallel development across repositories.
Quick Start
# Install and build
npm install
npm run build
# Run MCP server
beat mcp start
# or: node dist/cli.js mcp start
# Development mode (auto-reload)
npm run dev
# Test - Smart Grouping (v0.3.2+)
npm run test:core # Core domain logic (~3s) - SAFE in Claude Code
npm run test:handlers # Service handlers (~3s) - SAFE in Claude Code
npm run test:services # Service-layer tests (~2s) - SAFE in Claude Code
npm run test:repositories # Data layer (~2s) - SAFE in Claude Code
npm run test:adapters # MCP adapter (~2s) - SAFE in Claude Code
npm run test:implementations # Other implementations (~2s) - SAFE in Claude Code
npm run test:cli # CLI tests (~2s) - SAFE in Claude Code
npm run test:tmux # Tmux unit tests (~2s) - SAFE in Claude Code
npm run test:tmux:integration # Tmux integration tests (~3s) - SAFE in Claude Code
npm run test:channels # Channel tests (~3s) - SAFE in Claude Code
npm run test:integration # Integration tests - SAFE in Claude Code
npm test # ⚠️ BLOCKED - Prints warning and exits (technical safeguard)
npm run test:all # Full suite - Use in local terminal/CI only
npm run test:worker-handler # Worker tests (OPTIONAL)
npm run test:coverage # With coverage
Why grouped tests? Vitest workers accumulate memory across test files. Grouped tests provide fast feedback and prevent resource exhaustion. Individual groups are safe to run from Claude Code.
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 · 351 lines · 5,031 tokens per session scan A 96f04c36370b
autobeat CLAUDE.md is an instructions file published in the GitHub repository dean0x/autobeat (6 stars, last pushed 3mo ago), licensed MIT. It adds 5,031 tokens to every session, about $0.0252 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-31.
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).
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).
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.