opentrace: Instructions file for Claude Code

CLAUDE.md

opentrace CLAUDE.md is an instructions file for Claude Code from adham90/opentrace. It costs 953 tokens per session, scanned A, original, MIT.

A project guide for building and testing the opentrace Go application. It also records coding rules for its database, HTTP responses, errors, tests, and data handling.

In plain words
What is it for?
It helps with Go builds, short or full test runs, lint checks, database changes, API responses, logging, and updating test doubles when interfaces change.
Why use it?
It gives the coding agent consistent instructions for making changes that fit the existing project and for running the relevant checks.

Instructions file for Claude Code

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

This is adham90/opentrace's own configuration. It tells Claude Code how to work on opentrace 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 opentrace configures →

Reuse

Borrowing it

Nothing to install: this file belongs to adham90/opentrace. 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/adham90/opentrace/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/adham90/opentrace

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 opentrace CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/adham90/opentrace/claude-md/github.svg)](https://agentmods.dev/instructions/adham90/opentrace/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/adham90/opentrace/claude-md"><img src="https://agentmods.dev/badge/instructions/adham90/opentrace/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 opentrace CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/adham90/opentrace/claude-md"><img src="https://agentmods.dev/badge/instructions/adham90/opentrace/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 953 This file is loaded in full into every session.
When invoked 953 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.00953 $0.00953
Opus 5.5 $0.00381 $0.00381
Sonnet 5.5 $0.00191 $0.00191
Haiku 4.5 $0.00095 $0.00095

Measured 2mo ago against content hash fb06fc2f886a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

opentrace 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 2mo 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 · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Build & Test

go build -o opentrace ./cmd/opentrace
go test -short -race ./...          # unit tests (no Docker)
go test -race ./...                 # full suite (needs Docker)
go vet ./...                        # linting
go mod tidy                         # after adding new imports

Do

  • Use store.ErrNotFound sentinel for 404 responses
  • Use server.WriteJSON(w, status, data) / server.WriteError(w, status, msg) for HTTP responses
  • Use log/slog with structured key-value fields — always include "error" key on errors
  • Guard integration tests with testing.Short() skip
  • Use ? placeholders in SQLite queries — never string interpolation
  • Store booleans as INTEGER 0/1, timestamps as RFC3339 TEXT, UUIDs as TEXT
  • Cast MCP tool args from float64 (JSON default) before using as int
  • When adding a store interface method, update ALL mock implementations (internal/testutil/mocks/, internal/api/mock_test.go, and any package-local test doubles — grep the method name)
  • When adding a new store, add to pkg/store/ (interface + model) and internal/adapter/sqlite/ (implementation, wired in internal/adapter/sqlite/stores.go)
  • Use the server.Module pattern for new HTTP features — see internal/routes/<name>/module.go for examples
  • Run go mod tidy after adding new imports
  • Cap all pagination limit params to a reasonable maximum (100-500)
  • Validate and sanitize all user input at handler boundaries

Don't

  • Don't use fmt.Println or the old log package — use slog.* only
  • Don't shadow an imported package name with a local variable (e.g. a local watcher in a file that imports internal/watcher)
  • Don't use CGO — all dependencies must be pure Go for cross-compilation
  • Don't leak internal error details (SQL, file paths, stack traces) in HTTP responses
  • Don't add store fields directly to server.Deps — embed them in store.Stores instead
  • Don't skip testing.Short() guards on tests that need Docker or network
  • Don't hardcode magic numbers — use named constants
  • Don't write functions longer than ~100 lines — extract helpers

Read the full file on GitHub · 66 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. 2mo ago First seen · 66 lines · 953 tokens per session scan A fb06fc2f886a

Subscribe to this mod's changes

opentrace CLAUDE.md is an instructions file published in the GitHub repository adham90/opentrace (15 stars, last pushed 1mo ago), licensed MIT. It adds 953 tokens to every session, about $0.0038 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

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens