Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/armanfatemi/nullius/claude-mdgit clone --depth 1 https://github.com/armanfatemi/nulliusWhat 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 | $0.00964 | $0.00964 |
| Opus 5 | $0.00482 | $0.00482 |
| Sonnet 5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
nullius 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nullius
Deterministic checkers for agent-written claims. The thesis is that a model should only ever propose; verification is always code. Keep that boundary — if a change puts a model in the verification path, it is the wrong change.
Commands
pnpm build # required before any CLI use — dist/ is what the CLIs run
pnpm type-check
pnpm test
pnpm build first, always. The CLIs run from dist/, so an unbuilt tree
validates the previous version of the code and reports success on work that
does not exist yet.
Known-environmental test failures
src/flagConformance.test.ts fails 6 tests on machines where grep is
ugrep (macOS with ugrep installed). This is a real difference between the
declared flag table and the local binary, not a regression. Do not chase it,
and do not "fix" the table to match — CI runs real GNU grep and ripgrep.
Baseline: everything else passes. If you see 6 failures and they are all in that file, you have not broken anything.
Evidence Anchors — the house rule
Load-bearing claims about existing code carry a citation a checker re-verifies:
**Evidence:** `path/to/file.ts:88@a1b2c3d` — `const result = await retry(...)`
Rev-stamp anchors in openspec/changes/** from the start. Get the hash
with git rev-parse --short HEAD when you read the file. A change proposal
cites code it is about to modify, so an unstamped anchor there is designed to
rot — a design doc quoting a line as the reason to delete it becomes
FABRICATED the moment the change lands. With a stamp, the immutable claim
stays a hard gate and only the line number goes advisory (STALE).
Never repoint a line number while keeping an old stamp: that turns an advisory
STALE into a hard FABRICATED, because the text was not there at that commit.
Squash-merge destroys the commit a stamp names. This repo merges PRs with
merge commits for that reason — a squash leaves every anchor stamped against a
branch commit unreachable from main, and the checker then fails open with the
advisory UNVERIFIABLE-REV: CI stays green while the hard gate silently stops
existing. If a PR is squashed anyway, re-pin its anchors to the squash commit.
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.
- 2d ago First seen · 91 lines · 964 tokens per session scan A b7dec1adb317
nullius CLAUDE.md is an instructions file published in the GitHub repository armanfatemi/nullius (4 stars, last pushed 2d ago), licensed MIT. It adds 964 tokens to every session, about $0.0048 per session on Opus 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.
Other instructions, from other repositories
std-env AGENTS.md
Instructions for unjs/std-env, covering agents, project overview, maintenance, scripts and source structure.
mcp-adr-analysis-server copilot-instructions.md
Instructions for tosin2013/mcp-adr-analysis-server, covering mcp adr analysis server - ai coding agent instructions, project overview, critical technical conventions, esm-only module system and typescript configuration.
testivai-oss CLAUDE.md
Claude Code instructions for testivai/testivai-oss, covering testivai-oss — claude code guide, repo layout, package manager, common commands and architecture — how the oss lane works.
adrkit copilot-instructions.md
Instructions for mbeacom/adrkit, covering adrkit — github copilot and github copilot specifics.
adr-kit AGENTS.md
Instructions for rvdbreemen/adr-kit, covering adr-kit agent instructions, task management, repo conventions, verification and adr kit.
skilldrop CLAUDE.md
Instructions for sananthanarayan/skilldrop, covering claude.md, dogfooding a skill while you build it, then in a new claude code session in any repo, ${claudeskilldir} semantics and project settings.