Free tool

Set up your coding agent in one paste

MCP servers, project rules and command permissions for 13 agents, in one script you paste into your project folder. It writes each file where your agent reads it and never overwrites anything you already have. Every format comes from the same vendor-checked data as the rest of AgentAtlas.

1. Your agent

Paste in your project folder, or download

Writes .claude/rules/project.md, .claude/settings.json. Existing files are never overwritten.

# AgentAtlas setup for Claude Code: https://agentatlas.dev/tools/agent-setup
# Run from your project root. Existing files are never overwritten.
w() { f="$1"; mkdir -p "$(dirname "$f")"; if [ -e "$f" ]; then echo "exists: $f (wrote $f.agentatlas, merge it by hand)"; f="$f.agentatlas"; else echo "wrote: $f"; fi; cat > "$f"; }
w '.claude/rules/project.md' <<'AGENTATLAS_EOF'
- Use pnpm, not npm.
- Run the tests before you say a task is done.
- Never commit secrets or .env files.
AGENTATLAS_EOF
w '.claude/settings.json' <<'AGENTATLAS_EOF'
{
  "permissions": {
    "allow": [
      "Bash(npm test *)",
      "Bash(git status *)",
      "Bash(git diff *)"
    ],
    "deny": [
      "Bash(rm -rf *)",
      "Bash(git push --force *)"
    ]
  }
}
AGENTATLAS_EOF
See each file

.claude/rules/project.md (Project rules)

- Use pnpm, not npm.
- Run the tests before you say a task is done.
- Never commit secrets or .env files.

.claude/settings.json (Command permissions)

{
  "permissions": {
    "allow": [
      "Bash(npm test *)",
      "Bash(git status *)",
      "Bash(git diff *)"
    ],
    "deny": [
      "Bash(rm -rf *)",
      "Bash(git push --force *)"
    ]
  }
}

Just one part?

Agent setup formats change every month

Get one email a week when a coding agent moves a config file, renames a setting or adds a new one.