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/breadchaincoop/labor.fun/claude-mdgit clone --depth 1 https://github.com/BreadchainCoop/labor.funWrote 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/breadchaincoop/labor.fun/claude-md)<a href="https://agentmods.dev/instructions/breadchaincoop/labor.fun/claude-md"><img src="https://agentmods.dev/badge/instructions/breadchaincoop/labor.fun/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 | $0.01425 | $0.01425 |
| Opus 5 | $0.00713 | $0.00713 |
| Sonnet 5 | $0.00285 | $0.00285 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
labor.fun 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 3d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
labor.fun
A standalone, multi-org framework for multi-channel AI assistants. Runs
Claude agents in isolated containers with per-group memory. (Internal container
protocol keeps the nanoclaw codename.)
Quick Context
Single Node.js process. Channels (Telegram, Slack, Discord) self-register at startup. Messages route to Claude Agent SDK running in Docker containers. Each group has isolated filesystem and memory.
The framework is org-agnostic. Every org-specific thing — identity, KB, people, runtime state — lives in a profile under profiles/<name>/. The active profile is chosen at startup via LABOR_PROFILE (else the single profile present, else the repo root for legacy/dev). profile.config.json is the single source of truth for brand/identity/paths; the code reads it via src/profile.ts → src/config.ts. Never hardcode an org name, path, or GitHub org in src/ — derive it from the profile/config. See docs/NEW-ORG-GUIDE.md and docs/PLUGINS.md.
Rules & Operational Knowledge
Breadbrich Engels's behavior is defined by structured rule files in rules/. These are the authoritative source for:
| Rule Set | Path | Governs |
|---|---|---|
| Access Control | rules/access-control/ |
Who can see/do what, privacy enforcement |
| Knowledge Base | rules/knowledge-base/ |
KB structure, document format, task management |
| Messaging | rules/messaging/ |
Channel formatting, cross-platform send |
| Scheduling | rules/scheduling/ |
Cron tasks, scripts, API credit conservation |
| Identity & RBAC | rules/identity/ |
User resolution, tag hierarchy, platform mapping |
| Transcripts | rules/transcripts/ |
Meeting transcript processing, action item extraction |
| Approvals | rules/approvals/ |
Reusable human-in-the-loop approval primitive: gated action classes, who approves, expiry |
| GitHub Integration | rules/integrations/ |
GitHub issues/PRs/code/Actions on the org's GitHub org (githubOrg in the active profile) |
| Linear Integration | rules/integrations/ |
Linear issues/projects/comments in the org's Linear workspace (LINEAR_API_KEY) |
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.
- 3d ago First seen · 99 lines · 1,425 tokens per session scan A 6a843351fa3f
labor.fun CLAUDE.md is an instructions file published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 6d ago), licensed MIT. It adds 1,425 tokens to every session, about $0.0071 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.