agentleFS
ek33450505ek33450505/claude-agent-team/rules-core/agents.md

claude-agent-team / rules-core

AGENTS.md8 starsChanged 31 days agoMITView on GitHub

The file

We found no rules to list in this file: it reads as prose or reference rather than instructions.

Files
agents.md

Agent Definition Conventions

  • Agent definitions live in the REPO at agents/core/<name>.md — NOT at ~/.claude/agents/<name>.md
  • The runtime copy at ~/.claude/agents/ is managed by install.sh — never edit the runtime copy directly
  • Each agent file must have: role description, model assignment, behavioral rules, Status block requirement
  • Procedural memories for an agent are loaded at session start via cast-memory-router.py --mode retrieve --type procedural
  • ADM execution: the /orchestrate skill runs plans directly from the main session — no subagent dispatch needed for orchestration
  • Agent prompts in manifest dispatch: use subagent_type: 'general-purpose' for orchestrator dispatch workarounds
  • Model assignments vary per agent (13 haiku, 8 sonnet, 1 opus as of 2026-07-10) — see the agent-registry skill for the current per-agent mapping rather than assuming a blanket tier

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.