agent-registry
Skill0 starsChanged 3 months agoMITView on GitHub
Look up which agent or team owns a kind of work in this repository. Use when deciding whom to delegate to, when the user names a role, or when asked "who handles X".
5 other projects use a version of this.
Adopted by
Most recently taken up by
- ek33450505/claude-agent-teamtheir own version, first seen Oct 25, 2026
- sonichi/sutandotheir own version, first seen May 17, 2026
- 9thLevelSoftware/legiontheir own version, first seen May 5, 2026
- srinandan/agent-registry-skilltheir own version, first seen Apr 20, 2026
- MaTriXy/Agent-Registrytheir own version, first seen Feb 15, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- sonichi/sutando★ 396same name
- 9thLevelSoftware/legion★ 76same name
- MaTriXy/Agent-Registry★ 9same name
- ek33450505/claude-agent-team★ 7same name
- srinandan/agent-registry-skill★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/commands/agents.mdAGENTS.md
- .opencode/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/caveman.mdcCursor rule
- adrSkill
- cost-reviewSkill
- data-contractSkill
- delegation-protocolSkill
- marketplaceSkill
- onboardingSkill
- orchestrationSkill
- postmortemSkill
- runbookSkill
- threat-modelSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Read the candidate's Decision Rules section.
- Distinctive: line 58
If nothing fits, say so plainly and name the roster gap.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Registry
Where the roster lives
| File | Contents |
.claude/teams/README.md | Every agent: title, name, team, model |
.claude/teams/<team>.md | One team: mission, charter, roster with missions |
.claude/agents/<name>.md | One agent: all ten sections |
The name in frontmatter is what the Agent tool takes. It is the kebab-case slug.
Lookup procedure
- Reduce the request to a domain noun: "migration", "drift", "egress cost", "screen reader".
- Grep the roster for it.
.claude/teams/README.mdholds all 135 missions in one file. - Read the candidate's Decision Rules section. That is where an agent's real specialisation lives — two agents with similar titles differ there.
- Pick one. If two genuinely fit, pick the one whose Outputs match what you need, not the one whose title sounds closer.
Disambiguation — the pairs people confuse
| Question | Answer | Not |
| Design the schema | database-architect | database-engineer (tunes and migrates an existing one) |
| Build a metrics pipeline | observability-engineer | observability-test-engineer (verifies signals exist and are correct) |
| Write the model | ai-engineer | mlops-engineer (ships, versions, monitors it) |
| Is the model still good? | model-monitoring-engineer | ai-evaluation-engineer (builds the eval sets and metrics) |
| Cloud account hardening | cloud-security-engineer | platform-engineer (builds on it) |
| Corporate servers, patching, IAM | systems-administrator, iam-engineer | platform-engineer (product infrastructure) |
| Attack it | penetration-tester (authorised, proves exploitability) | security-test-engineer (in-CI security regression) |
| Watch the alerts | soc-analyst | incident-response-engineer (commands the response) |
| Cost of a design | cloud-cost-architect | finops-engineer (attributes and optimises a running bill) |
| Requirements | business-analyst (process and rules) | product-manager (what to build and why) |
Worked example
"Our S3 bill tripled last month."
- Domain noun: cost, running system, already spent.
finops-engineer— attribution and waste on an existing bill. First choice.cloud-cost-architect— only if the finding is architectural (egress pattern, storage class by design). Escalate to it after attribution, not before.data-engineer— pulled in if the driver turns out to be pipeline file-sizing.
Answer: finops-engineer first. Name the follow-ons as conditional, not parallel.
Rules
- One agent per concern. Do not fan out to five for a one-file change.
- Architects decide, engineers implement, quality verifies. Do not skip the middle.
- If nothing fits, say so plainly and name the roster gap. Do not force the nearest agent — a wrong specialist is more confidently wrong than a generalist.
Done when
- A single best-fit agent is named, with the
namevalue, not just the title. - The reason for the fit cites the agent's Decision Rules or Outputs, not its title.
- Near-misses are named as conditional follow-ons, not as parallel work.
- A genuine gap is reported as a gap.
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
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.

