Repo Agent Kit
Free AGENTS.md generator · no sign-up

Give your coding agent the context it keeps missing.

Turn your stack, commands, and guardrails into a clean instruction file for Codex, Claude Code, Cursor, or GitHub Copilot—in under a minute.

1

Describe your repository

Only include what the agent needs to work safely.

Guardrails to include

Live preview

AGENTS.md

179 words
# Acme dashboard

An internal analytics dashboard for operations teams.

## Start here
- Read the files nearest to the requested change before editing.
- Follow the existing Next.js, TypeScript, and Tailwind CSS patterns and preserve the current architecture.
- Use npm; do not introduce a second package manager or lockfile.
- Treat existing user changes as intentional. Never discard or overwrite them.

## Working rules
- Keep changes tightly scoped to the request. Avoid speculative refactors.
- Run `npm test` after changes and fix failures caused by your work.
- For UI work, preserve keyboard access, visible focus, semantic markup, and responsive behavior.
- Never expose secrets, credentials, private data, or local environment values.
- Explain non-obvious tradeoffs in the final handoff.

## Project-specific constraints
Do not change database migrations without explicit approval.

## Definition of done
- The requested behavior works end to end.
- Relevant checks pass and no new warnings are introduced.
- Changed code follows existing naming, formatting, and module boundaries.
- The handoff states what changed, what was verified, and any remaining risk.

Generated locally in your browser. Your project details are not uploaded.

New · manifest import

Already have a package.json or pyproject.toml?

Drop in one manifest and get a local, copy-ready AGENTS.md with detected commands—no CLI, upload, or API key.

Import a manifest

Why it works

A small file with an outsized effect.

Coding agents are better when the repository defines the boundaries. Repo Agent Kit turns vague preferences into instructions an agent can actually follow.

Preserve architecture

Tell the agent what to reuse, what not to rewrite, and how far a change should travel.

Define done

Make tests, checks, accessibility, and the final handoff part of the task—not an afterthought.

Protect the repository

Keep user changes, credentials, lockfiles, and migrations away from accidental damage.

One source, four formats

Switch agents without rewriting your standards.

The same repository contract becomes the right file and frontmatter for each major coding agent.

Convert an existing file Or generate one
New · public repo audit

Audit a GitHub repo—or generate its AGENTS.md.

Check readiness in a shareable report, then create an evidence-backed instruction file without an AI key.

See the 10-repository benchmark
Generate from GitHub Or audit readiness

Questions, answered.

What is an AGENTS.md file?

AGENTS.md is a repository instruction file that tells compatible coding agents how to work in a project: commands, conventions, guardrails, and the definition of done.

Where should I put AGENTS.md?

Place it at the repository root for project-wide guidance. Larger repositories can add more specific files inside subdirectories when local rules need to override the root guidance.

Does this work with Claude Code and Cursor?

Yes. Choose your agent and Repo Agent Kit changes the filename and, where needed, the file structure or frontmatter.

Can I check a public GitHub repository?

Yes. The repository audit checks public files without GitHub sign-in and creates a shareable readiness report. Private repositories are never requested.

Are my project details sent to a server?

No. The current generator builds and downloads the file entirely in your browser.