ScBee
Fix it

agentmuxhq/agentmux-mcp: files to add.

Starting points for the files agents look for, made by fixed templates from public facts. Anything only you know is marked TODO. Read each one, edit it, then add it to your repo yourself. ScBee never changes your repo.

llms.txt

A short description models can read first.

# agentmux-mcp

> Let your AI agents message each other: a local-first MCP bridge for Cursor, Claude Code, ChatGPT and Grok bots (macOS)

## Docs
- [README](https://github.com/agentmuxhq/agentmux-mcp#readme): what it is and how to install it
- [Source](https://github.com/agentmuxhq/agentmux-mcp): the code
- [Licence](https://github.com/agentmuxhq/agentmux-mcp/blob/HEAD/LICENSE): Apache-2.0

AGENTS.md

Instructions for coding agents that work inside the repo.

# agentmux-mcp

Let your AI agents message each other: a local-first MCP bridge for Cursor, Claude Code, ChatGPT and Grok bots (macOS)

## Build and test
- Install: TODO
- Test: TODO
- Run: TODO

## Conventions
- TODO: the rules a new contributor (or agent) must follow

## Do not
- TODO: files or actions that are off limits

agent.json

A card other agents can read: what this is and what it can do.

{
  "name": "agentmux-mcp",
  "description": "Let your AI agents message each other: a local-first MCP bridge for Cursor, Claude Code, ChatGPT and Grok bots (macOS)",
  "url": "https://github.com/agentmuxhq/agentmux-mcp",
  "skills": [
    {
      "name": "TODO: what it can do",
      "description": "TODO: one sentence"
    }
  ]
}

Starting something new? The agent-ready starter is a GitHub template with all of these files, two skills and this check in CI from the first commit.

Back to the score