janus-datalog: Instructions file for Claude Code

CLAUDE.md

janus-datalog CLAUDE.md is an instructions file for Claude Code from wbrown/janus-datalog. It costs 21,474 tokens per session, scanned A, original, Apache-2.0.

Development instructions for Janus Datalog, including its complete test command and architectural rules. The test gate checks native Go code, example programs, and JavaScript/WebAssembly contracts.

In plain words
What is it for?
Running the full test suite or focused checks, compiling examples, verifying WebAssembly contracts, and implementing approved architectural changes.
Why use it?
They prevent developers from treating partial tests as sufficient and clarify which architectural decisions belong to the project owner.

Instructions file for Claude Code

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

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

Reuse

Borrowing it

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

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 janus-datalog CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/wbrown/janus-datalog/claude-md"><img src="https://agentmods.dev/badge/instructions/wbrown/janus-datalog/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21,474 This file is loaded in full into every session.
When invoked 21,474 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.21474 $0.21474
Opus 5.5 $0.08590 $0.08590
Sonnet 5.5 $0.04295 $0.04295
Haiku 4.5 $0.02147 $0.02147

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

Security

Grade A, and why

janus-datalog 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 2d 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 · 1,729 lines

How it starts

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

Test Commands

The standard gate is make test. It runs the native suite (go test -count=1 ./...), the examples/ compile check (make test-examples), and the js/wasm contracts (make test-wasm). Do not treat bare go test ./... as a full green — that skips both of the others.

make test                        # Full gate: native + examples + wasm (required)
make test-examples               # Compile-check examples/ under //go:build example
make test-wasm                   # js/wasm contracts only (needs node)
go test -v ./package -run Test   # Focused native iteration only

Every examples/ file is its own package main behind //go:build example, so go vet ./examples/ reports main redeclared and no ordinary build reaches them. test-examples vets each file separately; without it nothing compiles them at all.

Do NOT add -timeout to go test commands, or use -timeout 0. Use the default timeout. No exceptions.


Architectural Authority

The user owns all architectural decisions. Claude implements them.

Before making ANY of these decisions, ASK:

  • Introducing new patterns (globals, managers, abstractions)
  • Changing existing patterns (options → globals, Relations → Bindings)
  • Adding new cross-cutting concerns (configuration, logging, caching)
  • Deviating from established conventions for any reason

If you're unsure whether something is an "architectural decision":

  • Would it affect multiple files/packages?
  • Would it change how components interact?
  • Would it require other code to change to accommodate it?
  • Are you thinking "I'll ask forgiveness later"?

Then ASK first.

Red flags that indicate you're overstepping:

  • "This is just temporary/experimental"
  • "I'll refactor this later"
  • "It's faster to do it this way"
  • "It's simpler/easier this way" (when deviating from a plan or established pattern)
  • Making a choice between multiple valid approaches without consulting

Read the full file on GitHub · 1,729 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. 2d ago Changed · +44 lines · +1,897 tokens per session e398954b1cb7
  2. 1mo ago Changed · +9 lines · +404 tokens per session b9eedc9825a1
  3. 1mo ago First seen · 1,676 lines · 19,173 tokens per session scan A 56607ce9510d

Subscribe to this mod's changes

janus-datalog CLAUDE.md is an instructions file published in the GitHub repository wbrown/janus-datalog (54 stars, last pushed today), licensed Apache-2.0. It adds 21,474 tokens to every session, about $0.0859 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