agentleFS
sametcelikbicaksametcelikbicak/opencode-team/docs/agents.md

opencode-team

AGENTS.md69 starsChanged 19 days agoMITView on GitHub

OpenCode Team defines 14 agent roles in agents/*.md. Every role uses mode: all, so it is reachable three ways: The orchestrator is the default agent. It routes an idea through the pipeline and asks for approval at each gate. A specialist owns one stage and writes that stage's artifact. In the build stage, fe and be write specialist reports and the orchestrator consolidates them into .team/07-build.md. Every agent is reachable directly: Directly invoked agents follow the same memory protocol as…

The file

We split this agents.md into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every agent is reachable directly:

    line 13
  2. Very specific:

    Create agents/<role>.md with frontmatter (description, mode: all, model (optional), permissions as an ordered array of {action, resource, …

    line 35
  3. Very specific:

    Add a command in commands/<role>.md if you want a direct entry point.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
agents.md

How agents work

OpenCode Team defines 14 agent roles in agents/*.md. Every role uses mode: all, so it is reachable three ways:

  • @agent-name to mention one directly
  • Shift+Tab (or /agents) to switch agents
  • the orchestrator can launch it as a subagent through the subagent tool

The orchestrator is the default agent. It routes an idea through the pipeline and asks for approval at each gate. A specialist owns one stage and writes that stage's artifact. In the build stage, fe and be write specialist reports and the orchestrator consolidates them into .team/07-build.md.

Direct invocation

Every agent is reachable directly:

@analyst
@pm
@po
@ux
@brand
@architect
@fe
@be
@qa
@security
@docs
@devops
@marketing

Directly invoked agents follow the same memory protocol as subagents: read .team/memory/INDEX.md and their own log, then write at most 5 lines to their own log.

Adding a role

  1. Create agents/<role>.md with frontmatter (description, mode: all, model (optional), permissions as an ordered array of {action, resource, effect}). The filename becomes the agent id; do not add name.
  2. Reference it in team.yaml as agent: <role>.
  3. Add a command in commands/<role>.md if you want a direct entry point.

Full list

Agent reference — generated from the filename and frontmatter: description, mode and model.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.