Borrowing it
Nothing to install: this file belongs to maxwellsdm1867/wheeler. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/maxwellsdm1867/wheeler/main/CLAUDE.mdgit clone --depth 1 https://github.com/maxwellsdm1867/wheelerWrote 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.
[](https://agentmods.dev/instructions/maxwellsdm1867/wheeler/claude-md)<a href="https://agentmods.dev/instructions/maxwellsdm1867/wheeler/claude-md"><img src="https://agentmods.dev/badge/instructions/maxwellsdm1867/wheeler/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.05892 | $0.05892 |
| Opus 5 | $0.02946 | $0.02946 |
| Sonnet 5 | $0.01178 | $0.01178 |
| Haiku 4.5 | $0.00589 | $0.00589 |
Grade A, and why
wheeler 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 7d 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 — 262 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.
What this codebase is
Wheeler is a Python package that turns Claude Code into a provenance-tracked research assistant. It is not an agent framework: there is no orchestration layer. Claude Code is the orchestrator; Wheeler provides (a) MCP tools that mutate a Neo4j knowledge graph, and (b) /wh:* slash commands that act as mode-restricted system prompts. Everything runs locally on a Max subscription via claude -p subprocess. No API keys are used, ever.
Version is 0.15.0. 3040+ tests (see the suite for the current count), 53 MCP tools across the four split servers. The legacy monolith has been removed.
Wheeler now runs on two agent hosts, Claude Code and OpenAI Codex, and ships as a plugin named wh rather than by copying files into ~/.claude/. The act bodies are served over MCP (get_act) so they exist in exactly one place; each host gets generated SKILL.md stubs. See "Multi-host distribution" below.
Commands
# Environment (Python 3.11+). uv is the primary workflow; the pip path
# remains supported for contributors without uv installed.
uv sync --extra dev # creates .venv/, installs from uv.lock
# or:
source .venv/bin/activate
pip install -e ".[test]" # core + test deps (fastembed + numpy are in core)
pip install -e ".[dev]" # full toolchain: tests + ruff + mypy + build
pip install -e ".[search]" # legacy no-op (fastembed+numpy already in core)
# Tests
python -m pytest tests/ -q # full suite, quiet
python -m pytest tests/test_merge.py -v # one file
python -m pytest tests/test_merge.py::TestExecuteMerge -v # one class
python -m pytest tests/ -k "consistency" # by keyword
python -m pytest tests/e2e/ -v # e2e, needs running Neo4j
python -m pytest tests/e2e/test_graph_first_acts.py -v # graph-first act workflows
python -m pytest tests/e2e/test_plan_lifecycle.py -v # plan lifecycle + triple-write
# E2E test philosophy: simulate the actual act workflow against live Neo4j.
# Each test walks through the exact tool-call sequence an act prescribes:
# 1. WRITE to graph (add_plan, ensure_artifact, add_finding, link_nodes)
# 2. READ back via the same query the act uses (query_plans, query_notes)
# 3. Verify graph state with direct Cypher (status, relationships, properties)
# 4. Verify triple-write artifacts on disk (knowledge/*.json, synthesis/*.md)
# This catches drift between what the act prompt says and what the graph
# actually stores. If an act says "call query_plans(status=approved)" but
# the query returns nothing because the status enum changed, the e2e test
# fails. Unit tests with FakeBackend can't catch that.
#
# TRAP when adding a live-Neo4j test late in the suite: graph_tools._get_backend()
# caches ONE module-level backend for the whole process, and each backend owns its
# own circuit breaker. Earlier tests push MagicMock values through that shared
# instance, which trips the breaker OPEN for 60s, so a live test placed after them
# fails with `circuit_open` while passing in isolation. Clear `_backend_instance`
# and call `invalidate_async_driver()` in your fixture's setup AND teardown.
# See tests/test_triple_write_project_root.py for the pattern.
#
# Also: the suite is sensitive to concurrent writers on one Neo4j. A red full-suite
# run in the asta/llmsr integration tests is worth re-running before treating it as
# a regression; those tests write and read back, so a second writer looks like a bug.
# Lint + type check (run by pre-commit hook)
.venv/bin/ruff check wheeler/
.venv/bin/mypy wheeler/ --ignore-missing-imports
# Git hooks (strongly recommended — block commits with API key leaks, broken tests, lint errors)
wh hooks install # copies .githooks/pre-commit + pre-push into .git/hooks/
wh hooks test # runs pre-commit checks without committing
# Headless Claude runs (for background tasks)
wh queue "prompt" # sonnet, 10 turns, structured JSON log to .logs/
wh quick "prompt" # haiku, 3 turns, one-shot
wh dream # graph consolidation (promotes tiers, detects communities, flags stale)
# MCP servers (launched by Claude Code via .mcp.json — not typically invoked by hand)
python -m wheeler.mcp_core # split: health/context/search/cypher/schema (12)
python -m wheeler.mcp_query # split: read-only query_* (11)
python -m wheeler.mcp_mutations # split: add_*, link, unlink, delete, merge, update (18)
python -m wheeler.mcp_ops # split: staleness, citations, consistency, ops (10)
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.
- 7d ago First seen · 262 lines · 5,892 tokens per session scan A 527e7e4eb22b
wheeler CLAUDE.md is an instructions file published in the GitHub repository maxwellsdm1867/wheeler (11 stars, last pushed 5d ago), licensed MIT. It adds 5,892 tokens to every session, about $0.0295 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
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.