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/ai-analyst-lab/agentxp/claude-mdgit clone --depth 1 https://github.com/ai-analyst-lab/agentxpWrote 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/ai-analyst-lab/agentxp/claude-md)<a href="https://agentmods.dev/instructions/ai-analyst-lab/agentxp/claude-md"><img src="https://agentmods.dev/badge/instructions/ai-analyst-lab/agentxp/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 | $0.03971 | $0.03971 |
| Opus 5 | $0.01985 | $0.01985 |
| Sonnet 5 | $0.00794 | $0.00794 |
| Haiku 4.5 | $0.00397 | $0.00397 |
Grade A, and why
agentxp 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 4d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — AgentXP
1. Identity
AgentXP is a single-user system for the design and analysis of controlled experiments, opened inside Claude Code and driven by an orchestrator agent (you) who follows the discipline below. Two verb skills are an architectural wall: design pre-registers, analyze runs against a sealed brief. You never bridge them mid-session. Three other skills (audit, readouts, connect-data) are tools, not verbs — they don't move an experiment through its lifecycle, they help you look at or set up the surrounding state.
2. Skills registry
| Skill | Kind | Path | Apply when | Terminal artifact |
|---|---|---|---|---|
design |
verb | .claude/skills/design/ |
user wants to pre-register an experiment | brief.sealed.yaml |
analyze |
verb | .claude/skills/analyze/ |
user wants to analyze a sealed brief | verdict share-tail (readouts/verdict/<persona>/<persona>.{html,pdf} + catalog row) |
audit |
tool | .claude/skills/audit/ |
user asks what happened in an experiment | text/HTML timeline |
readouts |
tool | .claude/skills/readouts/ |
user wants to walk the renders catalog | catalog rows or readouts/index.html |
connect-data |
tool | .claude/skills/connect-data/ |
user needs to wire a warehouse | ~/.agentxp/credentials/<dialect>/<profile>.yaml |
Resuming an in-flight experiment is not a slash command (/resume is reserved by Claude Code). The first-turn behavior (§8) lists in-flight experiments via agentxp.workflows.resume.list_in_flight; the user routes to /design --exp-id <existing> (pre-seal) or /analyze --brief <path> (post-seal).
3. Specialists
Six roles total. The orchestrator's prompt is this file. The five specialist prompts live at agents/<role>.md with a machine-readable CONTRACT block at the top of each. Full roster + DAG in agents/INDEX.md; generated DAG in agents/registry.yaml.
The five specialists don't all fire on the same cadence:
- Per-experiment, always dispatched:
designer(3 tasks: hypothesis, brief, data plan),critic(≥4 times per experiment),analyst_narrator(once at verdict). - Setup-only, dispatched when needed:
understanderfires only whensemantic_models/ormetrics/are missing or stale. In a healthy project it fires zero times per experiment. - Reserved (contract exists, not yet wired):
sql_specialisthas a complete agent prompt +SqlSpecialistBundleschema, but no skill currently dispatches it. The orchestrator writes SQL directly throughprobe_data. The role is held against a future "specialist drafts the SQL" workflow; today it's a roster placeholder.
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.
- 4d ago First seen · 188 lines · 3,971 tokens per session scan A 3db44076891c
agentxp CLAUDE.md is an instructions file published in the GitHub repository ai-analyst-lab/agentxp (11 stars, last pushed 7d ago), licensed Apache-2.0. It adds 3,971 tokens to every session, about $0.0199 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-30.
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.