gollem: Instructions file for Claude Code

CLAUDE.md

gollem CLAUDE.md is an instructions file for Claude Code from gollem-dev/gollem. It costs 2,227 tokens per session, scanned A, original, Apache-2.0.

A repository guide for Claude Code, the coding assistant, explaining its rules, development practices, and required checks for a Go project.

In plain words
What is it for?
It guides code changes, formatting, linting, security scans, test execution, comments, package layout, and safe use of temporary files and commands.
Why use it?
It keeps coding work consistent and prevents avoidable problems such as exposing unstable code, skipping security checks, or using the wrong test structure.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

This is gollem-dev/gollem's own configuration. It tells Claude Code how to work on gollem itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gollem configures →

Reuse

Borrowing it

Nothing to install: this file belongs to gollem-dev/gollem. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/gollem-dev/gollem/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/gollem-dev/gollem

Made for: Claude Code.

Wrote 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.

agentmods badge for gollem CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/gollem-dev/gollem/claude-md/github.svg)](https://agentmods.dev/instructions/gollem-dev/gollem/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/gollem-dev/gollem/claude-md"><img src="https://agentmods.dev/badge/instructions/gollem-dev/gollem/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for gollem CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/gollem-dev/gollem/claude-md"><img src="https://agentmods.dev/badge/instructions/gollem-dev/gollem/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,227 This file is loaded in full into every session.
When invoked 2,227 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02227 $0.02227
Opus 5.5 $0.00891 $0.00891
Sonnet 5.5 $0.00445 $0.00445
Haiku 4.5 $0.00223 $0.00223

Measured 25d ago against content hash 4ead662c8752, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gollem 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 25d 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.

CLAUDE.md · 233 lines

How it starts

The opening of the file, as written. The whole thing — 233 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.

Restriction & Rules

  • In principle, do not trust developers who use this library from outside
    • Do not export unnecessary methods, structs, and variables
    • Assume that exposed items will be changed. Never expose fields that would be problematic if changed
    • Use export_test.go for items that need to be exposed for testing purposes
  • When making changes, before finishing the task, always:
    • Run go vet ./..., go fmt ./... to format the code
    • Run golangci-lint run ./... to check lint error
    • Run gosec -quiet ./... to check security issue
    • Run tests to ensure no impact on other code
  • All comment and character literal in source code must be in English
  • Test files should have package {name}_test. Do not use same package name
  • Test must be included in same name test file. (e.g. test for abc.go must be in abc_test.go)
  • Use named empty structure (e.g. type ctxHogeKey struct{} ) as private context key
  • Do not create binary. If you need to run, use go run command instead
  • When a tmp directory is specified, search for files within the ./tmp directory relative to the project root.
  • Naming Convention: In Go, package names already express the subject, so avoid redundancy in method/struct names
    • Good: openai.New(), claude.WithModel(), gemini.ThinkingLevel
    • Bad: openai.NewOpenAIClient(), claude.WithClaudeModel(), gemini.GeminiThinkingLevel
  • Environment Variables: Outside of test code, NEVER use os.Getenv() or os.LookupEnv() directly. Always use github.com/urfave/cli/v3 for environment variable access
    • This ensures proper configuration management and testability
    • Test code may use os.Getenv() for test setup purposes

Commands

Development and Testing

  • task or task mock - Generate mock files for testing (uses moq)
  • go test ./... - Run all tests (MUST run before exiting tasks)
  • go test -v ./llm/openai/ - Run tests for specific package
  • go test -v ./path/to/package - Run specific package tests when developing
  • go build ./... - Build all packages
  • go mod tidy - Clean up dependencies

Read the full file on GitHub · 233 lines

Changes

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.

  1. 25d ago Changed · -1 lines · -26 tokens per session 4ead662c8752
  2. 26d ago Changed · +2 lines · +78 tokens per session 8094a5fda1fd
  3. 2mo ago First seen · 232 lines · 2,175 tokens per session scan A 389269e1c1a5

Subscribe to this mod's changes

gollem CLAUDE.md is an instructions file published in the GitHub repository gollem-dev/gollem (200 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,227 tokens to every session, about $0.0089 per session on Opus 5.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-30.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens