Proposal: Expand AGENT.md scope to cover sub-agents + enable interoperable linking with skills, hooks, and rules

Aperta
  • Qualcosa non va?
#149 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
documentation

Direzione di ricerca

Start by reading the existing AGENT.md conventions, then review the linked AgentSkills issue and Cursor and Claude Code references. Identify the minimal scope and schema for linking sub-agents, skills, hooks, and rules. Done means a concrete, backward-compatible proposal with agreed boundaries and conventions.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Hi AGENTS.md maintainers and community — thank you for the work on AGENT.md. I’m opening this issue as an open invitation to discuss evolving AGENT.md toward a broader, industry-aligned standard.

My motivation: agent ecosystems are rapidly adding more “configuration surface area” beyond a single instruction file — e.g., sub-agents, skills, hooks, and rules/policies (Cursor and others already expose these concepts). Right now, these efforts across communities look somewhat independent, and I think we’ll get better outcomes by coordinating.

The most important point

Today, sub-agents, skills, hooks, and rules should be seamlessly linked.
For instance, a sub-agent should be able to use agent skills. At the same time, we should clearly separate roles and responsibilities between:

  • what belongs in a sub-agent definition (persona, scope, delegation boundaries, defaults), and
  • what belongs in a skill (a reusable capability / tool contract),
    so the system stays maintainable as it grows.

What I believe AGENT.md could enable next

As far as I understand, AGENTS.md currently focuses on standardizing the AGENT.md file so different AI agents can load it consistently. That’s already valuable. I’d like to discuss whether we can extend the scope in two directions:

1) Broaden scope to include sub-agents

A natural extension is describing how a repository can declare:

  • sub-agent definitions (names, responsibilities, allowed actions, default prompts)
  • how sub-agents are discovered and loaded
  • how sub-agents reference skills/rules/hook policies

This could be done in a backward-compatible way (e.g., optional sections in AGENT.md, or a companion file like AGENTS/, or a simple directory convention).

2) Move toward an industry-level “plugin-like” packaging model

We may need something similar in spirit to custom Claude Code plugins, but at an industry level:

  • a way to bundle related resources (sub-agents + skills + rules + hooks + metadata)
  • versioning, isolation, reproducible installs, and governance controls (signing/verification, publisher identity)
  • interoperable across IDE/CLI tooling (Cursor, Claude Code, etc.)

Not prescriptive on the mechanism — but I think the outcome matters: reliable distribution and lifecycle management without config sprawl.

Concrete discussion questions

  1. What is in-scope for AGENTS.md long-term: only AGENT.md, or a broader “agent configuration contract”?
  2. If we include sub-agents, what is the minimal additional schema that provides value without overreaching?
  3. How should AGENT.md (or related conventions) express dependencies/links (sub-agent → skills; repo policies → hooks/rules)?
  4. Would maintainers be open to a joint working group / cross-repo discussion with AgentSkills (and others) to avoid diverging standards?

Why I’m raising this now

In practice, I’m seeing configuration fragmentation emerge quickly:

  • global folders like ~/.toolname/... become messy and hard to audit
  • resources drift out of sync across teams and machines
  • governance teams want consistent policy guardrails, but distribution is ad-hoc

A small amount of coordination now could prevent a lot of painful incompatibilities later.

References / context

Thanks for considering — happy to draft a concrete proposal (minimal schema / conventions) if there’s interest.

Links

Lingua principale
TypeScript
Stelle
24.8k
Fork
1.9k
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di agentsmd/agents.md

Tutte le issue di agentsmd/agents.md

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.