agents-md

Generate and maintain AGENTS.md files across monorepo workspaces.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/alexgorbatchev/ai-registry --skill agents-md-alexgorbatchev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents-md
Source: https://github.com/alexgorbatchev/ai-registry/tree/main/skills/agents-md
Command: npx skills add https://github.com/alexgorbatchev/ai-registry --skill agents-md-alexgorbatchev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Canonicalize and maintain AGENTS.md files across repositories to ensure consistent agent governance and avoid drift in instructions.

Core Features & Use Cases

  • Centralized AGENTS.md templates that cover commands, boundaries, and governance across multiple workspaces.
  • Nested-files support to accommodate divergent rules in monorepos, with quick references to maintenance workflows.
  • Incremental updates and pruning of boilerplate without sacrificing repository-specific signal.

Quick Start

Use the bootstrap workflow to generate or refresh AGENTS.md across the repository.

Frequently Asked Questions about agents-md

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize AGENTS.md files across a monorepo with nested workspaces?

Standardize AGENTS.md files across a monorepo by generating canonical templates and splitting into nested files where workspace rules diverge, ensuring consistent agent governance without instruction drift.

What is the best way to maintain AGENTS.md governance without accumulating boilerplate?

Maintain AGENTS.md governance by applying incremental, non-destructive updates that prune redundant boilerplate while preserving repository-specific signals like commands, boundaries, and references.

How does splitting AGENTS.md into nested files work for monorepos with divergent rules?

Splitting AGENTS.md into nested files accommodates divergent rules in monorepos by auditing existing instructions and distributing governance to specific workspace levels, preventing conflicting agent behaviors.

Can I audit and update existing AGENTS.md files without losing repository-specific instructions?

Auditing existing AGENTS.md files uses non-destructive updates to refresh canonical governance templates while preserving repository-specific commands, boundaries, and references essential to your workflow.

When do I need to generate canonical AGENTS.md files for repository governance?

Generate canonical AGENTS.md files when you need to establish consistent agent governance across multiple workspaces, ensuring all automated agents follow standardized operational boundaries and commands.