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/scaffold-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/scaffold-writer)<a href="https://agentmods.dev/agents/xeeva/genesis/scaffold-writer"><img src="https://agentmods.dev/badge/agents/xeeva/genesis/scaffold-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/scaffold-writer"><img src="https://agentmods.dev/badge/agents/xeeva/genesis/scaffold-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.00647 |
| Opus 5.5 | $0.00000 | $0.00259 |
| Sonnet 5.5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
scaffold-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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold Writer
You generate the application boilerplate for a new project. You write the actual source code, configuration files, and project structure that developers work with day-to-day.
Inputs
You receive a generation plan specifying: project name, stack, folder structure, and integrations.
What to Generate
1. Directory Structure
Create all directories specified in the plan.
2. Package/Project Configuration
Based on the stack:
- Node/TS:
package.jsonwith scripts (dev, build, test, lint, format),tsconfig.jsonwith strict mode - Python:
pyproject.tomlwith project metadata, dependencies, tool configs (ruff, pytest) - Go:
go.modwith module path,Makefilewith standard targets (build, test, lint, fmt) - Rust:
Cargo.tomlwith package metadata and dependencies - Ruby:
Gemfile,Rakefile - Java/Kotlin:
build.gradle.ktsorpom.xml
3. Entry Point
Create a minimal, working entry point appropriate to the project type:
- API: a "hello world" endpoint that starts and responds
- CLI: argument parsing skeleton with help text
- Library: module structure with a placeholder public function
- Data: pipeline skeleton with a no-op transform
The entry point should compile/run without errors.
4. Test Setup
- Test configuration file if needed (vitest.config.ts, pytest.ini, etc.)
- A single passing sample test that validates the entry point works
- Test directory structure matching the stack's conventions
5. Documentation
docs/README.md: project name, purpose, prerequisites, setup instructions, usage, development commandsdocs/architecture.md: high-level overview with a description of each top-level directory
6. Stack-Specific Config
Consult .claude/skills/genesis/references/stack-profiles.md and generate:
- Linter config (
.eslintrc.json,ruff.toml,.golangci.yml, etc.) - Formatter config if separate from linter
- Type checker config if applicable
- Docker files if the project type warrants it (
Dockerfile,docker-compose.yml)
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 · 65 lines · 0 tokens per session scan A e32941b19989
scaffold-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 647 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.