myco-rules

To keep canonical project rules consistent across multiple agents, maintain a single AGENTS.md file as the durable rules source and use thin agent-specific stubs that point to it, preventing drift and duplication across your repositories.

The best way to audit stale or duplicated rules in a multi-repo environment is to apply audit-ready guidance against your canonical AGENTS.md file, removing any duplicated or outdated rules to ensure strict governance and consistency across all agents.

To onboard a new project with a stable rules baseline, update AGENTS.md to reflect your canonical rules and refer to the canonical editing workflow to keep guidance stable and durable for all agents operating in the environment.

You need a canonical editing workflow for AGENTS.md when managing multi-repo, multi-agent environments that require strict governance, auditing, and onboarding, ensuring all changes are written durably to prevent rule duplication and drift.

Yes, you can use thin agent-specific stubs instead of duplicating rules in every repository; these stubs point directly to the canonical AGENTS.md file, ensuring all agents reference the same durable rules source without creating drift.

AGENTS.md prevents rule drift in multi-agent environments by acting as the single canonical source of truth for project rules, requiring all agents to reference it through thin stubs rather than maintaining independent rule sets.