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/beevibe-ai/beevibe/claude-mdgit clone --depth 1 https://github.com/beevibe-ai/beevibeWrote 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/beevibe-ai/beevibe/claude-md)<a href="https://agentmods.dev/instructions/beevibe-ai/beevibe/claude-md"><img src="https://agentmods.dev/badge/instructions/beevibe-ai/beevibe/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.02886 | $0.02886 |
| Opus 5 | $0.01443 | $0.01443 |
| Sonnet 5 | $0.00577 | $0.00577 |
| Haiku 4.5 | $0.00289 | $0.00289 |
Grade A, and why
beevibe 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 6d 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.
`curl -sS -o /dev/null -w '%{http_code}\n' https://fonts.googleapis.com/css2?family=Inter`. How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beevibe — Claude Code Guide
Monorepo structure
packages/
core/ shared domain, ports, services, adapters — compiled to dist/
api/ Express API + MCP server (tsx watch src/main.ts)
daemon/ Local agent runner (tsx watch src/main.ts start)
scheduler/ Cron + background jobs
web/ Next.js frontend
scripts/
dev.sh One-command local stack (postgres + core watch + api + scheduler)
Running locally
pnpm dev # everything: postgres, core watcher, api, scheduler, tunnel
pnpm dev --no-tunnel
pnpm dev now:
- Kills any stale beevibe processes from previous runs
- Starts
tsc --watchfor@beevibe/coreso source changes compile automatically - Starts API and scheduler (tsx watch, reload on file change)
The daemon is NOT started by pnpm dev — start it separately:
cd packages/daemon && npx tsx watch src/main.ts start
Critical: @beevibe/core compiles to dist/
packages/core/package.json exports point to ./dist/, not ./src/. Changes
to packages/core/src/** are invisible to the API and daemon until compiled.
pnpm dev now runs tsc --watch for core automatically. If you're not using
pnpm dev (e.g. running the API standalone), rebuild manually first:
pnpm --filter @beevibe/core build
After a core rebuild, touch a file in the consuming package to force tsx reload:
touch packages/api/src/runtime/router.ts # reload API
touch packages/daemon/src/spawner.ts # reload daemon
Restarting cleanly
pnpm dev uses trap 'kill 0' EXIT but only kills its own children. If you
close the terminal without Ctrl+C, tsx/node processes linger and hold ports.
To fully reset:
pkill -f "beevibe/(packages|scripts)"
pkill -f "daemon/src/main"
Or just run pnpm dev — it does this cleanup at the start now.
Agent runtime (Claude Code CLI)
- The CLI binary is
claudeon PATH - Sessions spawn with
--dangerously-skip-permissions --strict-mcp-config - MCP config lives in
~/.beevibe/workspaces/<agent_id>/mcp-config.json - Agent cwd is the workspace path (
~/.beevibe/workspaces/<agent_id>)
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.
- 6d ago First seen · 262 lines · 2,886 tokens per session scan A 297b141c72b6
beevibe CLAUDE.md is an instructions file published in the GitHub repository beevibe-ai/beevibe (345 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,886 tokens to every session, about $0.0144 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-30.
Other instructions, from other repositories
kungfu AGENTS.md
AGENTS.md instructions for kungfu-systems/kungfu, covering agents.md, start from the person's objective, rules that always apply, load bounded context before changing the repository and execute and verify through shifu.
kungfu copilot-instructions.md
Copilot instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before proposing or running changes. It is the shared agent router for this repository, including the canonical Shifu development and build entrypoint.
kungfu CLAUDE.md
Claude Code instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before working in this repository. It routes both product use and contribution work to the repository sources of truth, including the requirement that development and build tasks enter through Shifu.
build_a_product_agent CLAUDE.md
Instructions for ADW-19/build_a_product_agent, covering claude.md, 项目本质(readme 概览之外), 目录与编号规范, 文章写作规范(新增/修改文章时必须遵循) and 常用操作.
growmos AGENTS.md
Instructions for codician-team/growmos: This repository keeps a knowledge graph in .growmos/ (entities, typed relations, provenance, profiles, a journal). It is the shared world model that survives context windows. Treat it as memory you read at the start of work and write to as you develop. Zero-config commands.
pragma AGENTS.md
AGENTS.md instructions for pqpo/pragma, covering agents.md, 项目定位, 技术基线, 目录结构 and package 命名.