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/khromov/codebay/claude-mdgit clone --depth 1 https://github.com/khromov/codebayWhat 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 | $0.06586 | $0.06586 |
| Opus 5 | $0.03293 | $0.03293 |
| Sonnet 5 | $0.01317 | $0.01317 |
| Haiku 4.5 | $0.00659 | $0.00659 |
Grade A, and why
codebay CLAUDE.md scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Bridge / attention** (`src/lib/bridge.server.ts`): an in-memory, UI-only signal each container can raise — `done` (Claude finished) or `waiting` (Claude needs input) — to pulse its IDE tab. The injected Claude hooks `c How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this is
A web UI for spinning up isolated devcontainer instances from any local folder or Git repo URL, each exposing a browser-based VS Code (code-server). Pick a source → the app copies the folder (or clones the repo), injects code-server into its devcontainer.json, runs devcontainer up, and publishes the editor on a unique host port.
Runtime & commands
This runs on Bun only (Node.js is not supported). The app is built on Mochi, an SSR Svelte 5 framework with islands-based selective hydration, installed from npm as mochi-framework.
bun run dev # dev server (MODE=development, project-local DATA_DIR, no browser launch)
bun run start # runs src/index.ts directly (no separate build step needed)
bun run build # mochi-framework build → .mochi/
bun run typecheck # svelte-check (with a custom warning-ignore flag) + tsc --noEmit; run after any TS/Svelte change
bun test # all tests
bun test src/index.isolated.test.ts # single file
bun test -t "renders Hello world" # single test by name
bun run checks # format + eslint + typecheck + tests — run this after every change (see below)
bun run clean # remove .mochi build output
bun run lint # prettier --check + eslint (read-only; `checks` runs format instead of prettier --check, but the same eslint)
bun run gen:chimes # re-render attention chimes to public/sounds/ WAVs (after editing scripts/gen-chimes.ts)
bun run prod # build + serve the production bundle
bun run verify:package # pack the tarball, install + boot it elsewhere (see npm packaging below)
Always run bun run checks after implementing a change (it runs format, then eslint, then typecheck, then test) and fix anything it surfaces before considering the work done.
Docker availability & testing strategy. The automated suite (bun test / bun run checks) is fully self-contained — even docker.isolated.test.ts stubs dockerode via globalThis.__codebayDocker, so no Docker daemon is required and the checks always run (e.g. inside the Bun-only .devcontainer/, which deliberately has no Docker access). Only end-to-end verification of the instance lifecycle — actually creating an instance, devcontainer up, the boot/health flow — needs a live daemon. Before attempting any such live verification, probe with docker info (or docker context inspect): if it's unavailable, don't try to boot instances — say so and fall back to the unit/isolated tests, which cover the orchestration logic against stubs. When Docker is running, live-boot verification becomes an option on top of the suite.
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.
- 2d ago First seen · 115 lines · 6,586 tokens per session scan A 52074844a29d
codebay CLAUDE.md is an instructions file published in the GitHub repository khromov/codebay (10 stars, last pushed 3d ago), licensed MIT. It adds 6,586 tokens to every session, about $0.0329 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
microsandbox AGENTS.md
AGENTS.md instructions for superradcompany/microsandbox, covering agents.md, scope, project map, design principles and backward compatibility review.
ratel AGENTS.md
Instructions for ratel-ai/ratel, covering agents.md — working in the ratel repo, build & test, rust, ts and python (from src/sdk/python/; needs uv).
swift-tui AGENTS.md
Instructions for SwiftTUI/swift-tui, covering agents.md, build & test commands, architecture (one-page summary), development guidelines and code style.
best-claude-hud AGENTS.md
Instructions for GaoSSR/best-claude-hud, covering project agent instructions and release work.
dotfiles AGENTS.md
Instructions for sebastienrousseau/dotfiles, covering project overview, key commands, repository layout, chezmoi naming conventions and conventions.
mcp-screenshot-server CLAUDE.md
Instructions for sethbang/mcp-screenshot-server, covering claude.md, what this is, commands, environment variables and architecture.