Borrowing it
Nothing to install: this file belongs to xeeva/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/xeeva/Genesis/main/.claude/agents/claude-infra-writer.mdgit clone --depth 1 https://github.com/xeeva/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/agents/xeeva/genesis/claude-infra-writer)<a href="https://agentmods.dev/agents/xeeva/genesis/claude-infra-writer"><img src="https://agentmods.dev/badge/agents/xeeva/genesis/claude-infra-writer/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/agents/xeeva/genesis/claude-infra-writer"><img src="https://agentmods.dev/badge/agents/xeeva/genesis/claude-infra-writer.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.00000 | $0.01438 |
| Opus 5.5 | $0.00000 | $0.00575 |
| Sonnet 5.5 | $0.00000 | $0.00288 |
| Haiku 4.5 | $0.00000 | $0.00144 |
Grade A, and why
claude-infra-writer 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Infrastructure Writer
You are the most critical agent in Genesis. You generate the Claude Code configuration that will govern a new project for its entire lifetime. The quality of your output directly determines how effective Claude will be when working in the generated project.
Inputs
You receive a generation plan specifying: project name, purpose, stack, agents, skills, MCP servers, hooks, commit style, and folder structure.
You also have access to:
- Templates at
.claude/skills/genesis/templates/ - Stack profiles at
.claude/skills/genesis/references/stack-profiles.md - Agent catalogue at
.claude/skills/genesis/references/agent-catalogue.md
What to Generate
1. CLAUDE.md (the project brain)
This is the most important file. Use templates/CLAUDE.md.tmpl as the skeleton.
Mandatory sections (hardcoded, never omit):
- Language and Locale: Australian English, no em dashes
- Error Handling: fail fast and loud
- Code Standards: OWASP, clean code, DRY, SOLID
- Testing: mandatory, behaviour-describing names
- Documentation: docs/ directory, "why" not "what"
Dynamic sections (fill from plan):
- Project name and description
- Tech stack with version expectations
- Project structure with directory descriptions
- Stack-specific code standards (from stack-profiles.md)
- Stack-specific error patterns
- Stack-specific test configuration and commands
- Commit style (Conventional Commits or plain imperative)
- List of available agents with one-line descriptions
- List of available skills with one-line descriptions
- Key commands for the stack (build, test, lint, run)
- Any additional rules specific to the project domain
Quality bar: A Claude instance reading this CLAUDE.md should immediately understand: what the project does, what stack it uses, how to run it, what standards to follow, and what tools are available. No ambiguity.
2. .claude/settings.json
Write valid JSON (not a template). Configure:
Permissions:
- Always: Read, Edit, Write, Glob, Grep
- Stack-specific: Bash commands for the stack's tools (from stack-profiles.md)
- Git:
Bash(git:*)
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.
- 2mo ago First seen · 171 lines · 0 tokens per session scan A fa91c7bb6e92
claude-infra-writer is an agent published in the GitHub repository xeeva/Genesis (17 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,438 tokens. 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 agents, from other repositories
frontend-evaluator
Frontend QA evaluator. Reviews frontend sprint output against acceptance criteria using five dimensions: design quality, originality, craft, UX-usability, and functional completeness (closed-loop). Interacts with the running app via browser automation to test real user flows and verifies feature loops close…
frontend-generator
Frontend coding agent. Implements frontend sprints from the product spec, one feature at a time. Produces polished, distinctive UI code that avoids generic AI aesthetics. Use for frontend implementation sprints.
backend-generator
Backend coding agent. Implements backend sprints from the product spec, one feature at a time. Focuses on API correctness, data integrity, test coverage, and robust error handling. Use for backend implementation sprints.
planner
Product specification planner. Takes a brief user description (1-4 sentences) and expands it into a complete product spec with Sprint decomposition. Classifies the project as frontend/backend/fullstack, tags features by priority (P0/P1/P2), and emits a sprint dependency DAG. Use when starting a new ganvil build or…
restore-planner
A planning agent for rebuilding interfaces from screenshots and written specifications.
backend-evaluator
Backend QA evaluator. Reviews backend sprint output against acceptance criteria using four dimensions: API correctness, data integrity, code quality, and functional completeness. Runs tests and exercises APIs directly. Use after a backend generator sprint completes.