lotor: Instructions file for Claude Code

CLAUDE.md

lotor CLAUDE.md is an instructions file for Claude Code from githubscum/lotor. It costs 649 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for Lotor, a local-first receipt and approval gate for coding-agent sessions. A local-first tool keeps its main records on the user's machine.

In plain words
What is it for?
Use them when editing Lotor, interpreting its pre-action gate messages, staging a risky action, or running the documented approval command.
Why use it?
They explain how to work in the repository when an action is blocked by a gate, including what the warning means and how approval works.

Instructions file for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: reads .claude/ paths; mentions CLAUDE.md.

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/githubscum/lotor/claude-md"><img src="https://agentmods.dev/badge/instructions/githubscum/lotor/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 649 This file is loaded in full into every session.
When invoked 649 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.00649 $0.00649
Opus 5.5 $0.00260 $0.00260
Sonnet 5.5 $0.00130 $0.00130
Haiku 4.5 $0.00065 $0.00065

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

Security

Grade A, and why

lotor 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 · 26 lines

How it starts

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

CLAUDE.md — working in this repo

This is Lotor: a local-first receipt layer and gate for agent sessions. Its own thesis is structural, not behavioral — a rule enforced by code holds regardless of which model is enforcing it; a rule left to a model's judgment produces a different experience every time a different model runs it. That applies to how you, the agent working in this repo, behave when the gate fires.

When the gate blocks you

The PreToolUse hook denies with exit code 2 and prints a fixed-shape message: a plain-English title (with the rule id as a technical suffix), what matched, any agent-stated purpose labelled as unverified, why it matters, how risky it is, exactly what the signature does and does not cover, and one command that runs as printed (npm run approve -- --request <id>). That message is designed to stand on its own. Read cold, by a human who has read none of this file, it should still be enough to decide.

Your job around that message has four beats. Do all four, in order, every time:

  1. Stage first. Never let the gate be the first thing the owner hears about. If you are about to do something you expect to be gated (editing a bin/*.js hook, src/policy/, src/gate/, .claude/settings.json, or anything else self-mod protects), say so before you attempt it, and prefer writing the artifact somewhere reviewable first when that is practical.

  2. Give the path. If a file was created or changed, state its path so the owner can open and read it themselves, before a signature is requested. Do not ask for a signature on something the owner has not had the chance to see.

  3. Relay, do not rewrite. When the gate denies, paste its stderr output as-is. Do not summarize it, soften it, translate its risk language into something gentler, or decide on the owner's behalf that a warning doesn't apply this time. The message was written to be complete; your job is to deliver it, not edit it.

  4. Wait. No retry loop, no alternate route around the block, no quietly finding an unprotected path that achieves the same end. State plainly what stays undone until it is signed, then stop and let the owner act.

Read the full file on GitHub · 26 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 · 26 lines · 649 tokens per session scan A eb61162bdceb

Subscribe to this mod's changes

lotor CLAUDE.md is an instructions file published in the GitHub repository githubscum/lotor (3 stars, last pushed 8d ago), licensed Apache-2.0. It adds 649 tokens to every session, about $0.0026 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-31.

Related

lotor CLAUDE.md compared with instructions from other repositories

lotor CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
lotor CLAUDE.mdgithubscum/lotorInstructions file38d agoApache-2.0A649Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,685GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,086GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file281ktodayMITA4,335Codex, OpenCode