FREE TOOL

AGENTS.md Generator

Structured agent instructions. Live preview. Clean Markdown export. Shareable links.

Draft the file coding agents read first - build commands, conventions, layout, and security notes. No account. Nothing leaves your browser until you commit the file.

AGENTS.md vs CLAUDE.md vs llms.txt

Project nameSummary for agentsOne or two sentences: what the repo is and how agents should approach changes.Build commandsOne command per line - exported as a runnable code block.Test commandsOne command per line - what agents run to verify their changes.Code styleOne rule per line - each becomes a bullet.ConventionsOne rule per line - where things live and patterns agents should not guess.Repository layoutOne entry per line as “path - what it is”.PR & commit guidelinesOne rule per line - checks to run, title format, review expectations.Security notesOne rule per line - secrets handling and operations needing human review.

Live preview

Acme Payments API

TypeScript monorepo for billing, subscriptions, and Stripe webhooks. Prefer small, reviewable PRs with tests for payment and auth paths.

Build commands

npm install
npm run build

Test commands

npm run test
npm run lint

Code style

Use TypeScript strict mode.
Prefer explicit return types on exported functions.
Keep modules focused - one domain per folder under src/lib/.

Conventions

Stripe webhook handlers live in src/lib/billing/.
Never log secrets or full card numbers.
All billing mutations go through subscription-items.ts helpers.

Repository layout

apps/web - Next.js dashboard and API routes
packages/shared - shared types
supabase/migrations - database schema

PR & commit guidelines

Run the full test suite before opening a PR.
Keep PRs to one logical change; billing and auth changes need a test.
Title format: [area] Short imperative summary.

Security notes

Do not commit .env files.
Webhook routes must verify Stripe signatures before dispatching events.

AGENTS.md is the front door - Moxie keeps what it points to accurate Export free above · connect a repo when you want Moxie to keep it accurate

Read the AGENTS.md guide See how Moxie keeps docs current

Agent-first structure

Runnable command blocks, one-rule-per-bullet conventions, repository layout, PR guidelines, and security notes - the structure agents actually parse.

Live preview

See the rendered AGENTS.md as you type. No separate export step to review formatting.

Shareable & portable

The full draft lives in the URL. Send the link or bookmark it. Export clean Markdown ready for your repo root.

Private by design

Everything runs in your browser. Instructions never leave your device until you commit the file.

What to put in AGENTS.md

Build and test commands

The exact commands agents should run before and after edits - install, build, lint, and test.

Conventions and layout

Where modules live, naming patterns, and rules agents should not guess from file names alone.

Security boundaries

Secrets handling, auth paths, and operations that require human review before an agent proceeds.

Pointers to deeper docs

Link to architecture pages or an llms.txt index when agents need more than a single-repo cheat sheet.

Frequently asked questions

What is AGENTS.md?

AGENTS.md is a Markdown file at your repository root that gives coding agents project-specific instructions: how to build and test, code style, conventions, layout, PR guidelines, and security notes. It is the front door agents read before editing your codebase.

How is AGENTS.md different from CLAUDE.md or llms.txt?

AGENTS.md is a single-repo instruction file for any agent. CLAUDE.md is Claude-specific. llms.txt is a site-wide index of URLs for crawlers. Our guide walks through when to use each and how they work together.

Is this AGENTS.md generator free?

Yes. Use it as much as you want. No sign up, no limits, no watermarks. The output is plain Markdown you can commit anywhere.

Can I share a work-in-progress AGENTS.md?

Yes. Use the Share link button. The full state is encoded in the URL so the recipient sees exactly what you have so far.

How do I keep AGENTS.md accurate over time?

AGENTS.md drifts the moment conventions or commands change. Moxie Docs indexes your repository, extracts real conventions from code, and keeps AGENTS.md and linked docs current on every merge - with reviewable Cleanup PRs.

Does Moxie replace writing AGENTS.md by hand?

This tool helps you draft and export AGENTS.md quickly. When you connect GitHub, Moxie can populate conventions from source, surface doc gaps, and serve the same context over MCP so agents read what the code does now.