Borrowing it
Nothing to install: this file belongs to Evolvlabsai/Exolvra-Genesis. 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/Evolvlabsai/Exolvra-Genesis/main/CLAUDE.mdgit clone --depth 1 https://github.com/Evolvlabsai/Exolvra-GenesisWrote 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/evolvlabsai/exolvra-genesis/claude-md)<a href="https://agentmods.dev/instructions/evolvlabsai/exolvra-genesis/claude-md"><img src="https://agentmods.dev/badge/instructions/evolvlabsai/exolvra-genesis/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.
<a href="https://agentmods.dev/instructions/evolvlabsai/exolvra-genesis/claude-md"><img src="https://agentmods.dev/badge/instructions/evolvlabsai/exolvra-genesis/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01839 | $0.01839 |
| Opus 5 | $0.00920 | $0.00920 |
| Sonnet 5 | $0.00368 | $0.00368 |
| Haiku 4.5 | $0.00184 | $0.00184 |
Grade A, and why
Exolvra-Genesis 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 9d 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 — 78 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 repository is
Exolvra Genesis is an adversarial orchestration loop for Claude Code — builder subagents iterate against blind, fresh-context critics comparing real output to a concrete quality bar, until the assembled work wins twice in a row. It ships two ways from one source of truth:
- The plugin (
commands/,agents/,templates/,hooks/): plain Markdown plus one HTML template. The wording is load-bearing — editing these files is editing behavior. - The CLI (
cli/): a TypeScript package exposing anexolvra-genesisbin that runs the same loop without opening Claude Code. It is transport and ergonomics only; it loads the plugin files at runtime and never restates them. The CLI was built by its own loop (24 judged rounds againstcli/cli-spec.md, ending on two consecutive blind critic WINs).
Commands
Plugin (no build tooling — test by installing and running):
/plugin marketplace add <path-to-this-repo>
/plugin install exolvra-genesis@exolvra-genesis
/exolvra-genesis:run <goal or spec path> # prefix args with `auto` to skip the approval pause
/exolvra-genesis:interview [spec or idea] # produces a run-ready spec + HTML mockup
CLI (from cli/):
npm install && npm run build # build also copies the plugin files into dist/plugin
npm run typecheck # tsc --noEmit
npm test # node --test, 677 tests; the packaging test is slow (~150s)
node --test test/<file>.test.js # one suite, no rebuild
The full suite is the gate for any CLI change. One known flake: a usage test can time out while the packaging test saturates the machine; it passes in isolation and on rerun.
Architecture
The loop lives entirely in the plugin Markdown:
commands/run.md— the lead agent. Captures the bar into.exolvra-genesis/bar/(pinned twice:BAR.mdfor people,bar.sha256for the integrity hook; immutable per run), decomposes into Task Specs, fans out builders, re-runs their verification itself, dispatches fresh critics with shuffled labels, maintains the progress page fromtemplates/progress.html, and enforces the win condition.commands/interview.md— one-question-at-a-time interview producing a spec plus a single-file interactive mockup. A conversation, not a build; no subagents.agents/builder.md(exolvra-genesis-builder) — implements exactly one Task Spec; touches only owned files; reports only FILES CHANGED / COMMANDS RUN / VERIFICATION (verbatim).agents/critic.md(exolvra-genesis-critic) — blind judge; sees only the bar and the real output. VERDICT (WIN/LOSS, or BLOCKED only for a missing perception capability — e.g. a visual bar with no browser/screenshot tool) / GAP / EVIDENCE. A tie is a LOSS.
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.
- 9d ago First seen · 78 lines · 1,839 tokens per session scan A ddd75c2503ed
Exolvra-Genesis CLAUDE.md is an instructions file published in the GitHub repository Evolvlabsai/Exolvra-Genesis (1 stars, last pushed 20d ago), licensed MIT. It adds 1,839 tokens to every session, about $0.0092 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).
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.
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.