Borrowing it
Nothing to install: this file belongs to 0xranx/golembot. 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/0xranx/golembot/main/CLAUDE.mdgit clone --depth 1 https://github.com/0xranx/golembotWrote 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/0xranx/golembot/claude-md)<a href="https://agentmods.dev/instructions/0xranx/golembot/claude-md"><img src="https://agentmods.dev/badge/instructions/0xranx/golembot/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.01141 | $0.01141 |
| Opus 5 | $0.00571 | $0.00571 |
| Sonnet 5 | $0.00228 | $0.00228 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
golembot 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
5. **Process invocation is engine-owned** — All engines use `child_process.spawn`. Do not assume invocation style outside the engine. How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GolemBot — Project Conventions for Claude Code
This file is the Claude Code equivalent of
.cursor/rules/*.mdc. It is auto-loaded at conversation start and provides project-level constraints.
Architecture Hard Constraints
When modifying code under src/, the following constraints must not be violated.
Things You Must Never Do
- Don't do what the Agent should do — GolemBot does not manage context window, dispatch tools, reason, or set session TTL. All "intelligent" behavior is delegated to the underlying Coding Agent.
- Don't add new core concepts — The framework has only two concepts: assistant directory + Skill. Do not introduce Tool, Blueprint, Registry, Pipeline, or other abstractions.
- Don't put CLI logic in the core library —
cli.tsis a thin shell; it only parses arguments and formats output. All business logic must live inindex.ts/workspace.ts/engine.ts/session.ts/server.ts. - Don't declare Skills in config — The
skills/directory is the single source of truth.golem.yamlonly configures engine, name, and infrastructure settings. - Process invocation is engine-owned — All engines use
child_process.spawn. Do not assume invocation style outside the engine.
Interface Change Rules
- Any signature change to the
Assistantinterface (index.ts) must be verified acrossserver.ts,gateway.ts, andcli.ts. - Any change to the
AgentEngineinterface (engine.ts) must remain compatible with all engines (Cursor, Claude Code, OpenCode, Codex). StreamEventtype changes must verify compatibility withserver.tsSSE output,cli.tsevent handling, andgateway.tsIM message assembly.
File Responsibility Boundaries
| File | Responsibility | Should Not Contain |
|---|---|---|
index.ts |
Public API, concurrency locks, orchestration of workspace/engine/session | Engine implementation details, HTTP logic |
engine.ts |
Engine interface, all engine implementations, stream-json parsing, Skill injection | Session management, config loading |
workspace.ts |
golem.yaml read/write, skills scanning, AGENTS.md generation | Engine invocation, session management |
session.ts |
Session persistence (indexed by sessionKey) | Any other logic |
server.ts |
HTTP service, SSE, auth | Engine implementation details |
gateway.ts |
HTTP API + IM channel orchestration | Engine implementation details |
cli.ts |
Argument parsing, call core API, format output | Business logic |
cli-utils.ts |
CLI formatting helpers (tool display, truncation) | Business logic |
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 · 103 lines · 1,141 tokens per session scan A 9a41ab2c00db
golembot CLAUDE.md is an instructions file published in the GitHub repository 0xranx/golembot (320 stars, last pushed yesterday), licensed MIT. It adds 1,141 tokens to every session, about $0.0057 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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).
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.