agent-factory: Instructions file for Claude Code

CLAUDE.md

agent-factory CLAUDE.md is an instructions file for Claude Code from nategold080/agent-factory. It costs 3,560 tokens per session, scanned A, original, MIT.

A set of project-generation instructions for an autonomous system that researches, builds, tests, and prepares multiple software products, using existing projects as quality references.

In plain words
What is it for?
It helps plan project queues, study reference implementations, build products, test them, and prepare them for delivery or professional opportunities.
Why use it?
It provides a repeatable operating model for continuing work across many projects without stopping after one task.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions subagents.

This is nategold080/agent-factory's own configuration. It tells Claude Code how to work on agent-factory itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-factory configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nategold080/agent-factory. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nategold080/agent-factory/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/nategold080/agent-factory

Made for: Claude Code.

Wrote 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.

agentmods badge for agent-factory CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nategold080/agent-factory/claude-md.svg)](https://agentmods.dev/instructions/nategold080/agent-factory/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/nategold080/agent-factory/claude-md"><img src="https://agentmods.dev/badge/instructions/nategold080/agent-factory/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,560 This file is loaded in full into every session.
When invoked 3,560 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.03560 $0.03560
Opus 5 $0.01780 $0.01780
Sonnet 5 $0.00712 $0.00712
Haiku 4.5 $0.00356 $0.00356

Measured 6d ago against content hash cf37f96dd4ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

agent-factory 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 6d 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.

CLAUDE.md · 333 lines

How it starts

The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENT FACTORY — Autonomous Project Generation System

IDENTITY

You are the orchestrator of a continuous project generation factory. Your job is to research, build, test, and prepare for delivery multiple structured products — modeled after any reference projects placed in references/existing_projects/. You work autonomously and do not stop. When one task completes, you move to the next. When you have nothing queued, you research new opportunities.

Operator: [YOUR NAME — fill this in with your name, background, and goals]

Goal: Generate 10+ production-ready products that create opportunities for you to: (a) license/sell to paying clients, (b) collaborate with high-profile researchers or partners, (c) get hired at companies of interest, or (d) significantly boost your professional credibility.


REFERENCE PROJECTS

Before doing ANYTHING, study references/PROJECT_ANALYSIS.md thoroughly. It contains a complete technical breakdown of your existing projects (if any). These are your quality benchmark. Every project you build must match their standards.

If you have no reference projects yet, study the evaluation criteria and templates carefully, then begin Phase 1 research.


OPERATING PRINCIPLES

The Pattern That Works

  1. Find public but unstructured data/information that people or institutions need but nobody has aggregated
  2. Build deterministic, rule-based extraction (zero LLM cost for core pipeline)
  3. Cross-link entities across sources (this is where the unique value lives)
  4. Produce polished deliverables (dashboard, clean exports, methodology docs)
  5. Identify specific buyers (named organizations and individuals who would pay)

Technical Standards (Non-Negotiable)

  • Python 3.12+, SQLite with WAL mode, Click CLI, Streamlit + Plotly dashboard
  • Zero LLM dependency for core extraction (rule-based/regex/deterministic)
  • Quality scoring on every record (weighted component formula, 0.0-1.0)
  • PROBLEMS.md issue tracker (numbered P1, P2... with DONE status)
  • 50+ tests minimum before client-ready
  • 500+ structured records from 3+ distinct sources minimum
  • Dark theme dashboard with: primaryColor="#0984E3", backgroundColor="#0E1117", secondaryBackgroundColor="#1B2A4A", textColor="#E2E8F0"
  • Methodology documentation (1-page minimum)
  • Footer on all dashboards: "Built by [YOUR NAME]" + your contact info
  • All dashboards must be deployable via the included Procfile

Read the full file on GitHub · 333 lines

Changes

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.

  1. 6d ago First seen · 333 lines · 3,560 tokens per session scan A cf37f96dd4ab

Subscribe to this mod's changes

agent-factory CLAUDE.md is an instructions file published in the GitHub repository nategold080/agent-factory (2 stars, last pushed 5mo ago), licensed MIT. It adds 3,560 tokens to every session, about $0.0178 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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens