1. Conduid
  2. Developer Tools
  3. Sub Agents.directory
MCP server · Developer Tools

Sub Agents.directory

by · github.com/ayush-that/sub-agents.directory

Sub-Agents Directory is a curated collection of 100+ sub-agent prompts and MCP servers for Claude Code.

Unclaimed MIT last commit 6 months ago subagentsai-agentsclaudeclaude-aidevtoolsclaude-subagents
InstallView source
72Good

Scored 4 months ago · breakdown

About Sub Agents.directory

Sub Agents.directory is an MCP server published by ayush-that in the Developer Tools category: sub-Agents Directory is a curated collection of 100+ sub-agent prompts and MCP servers for Claude Code. It has been installed 0 times through Conduid.

The repository has 96 stars and 21 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx sub-agents-directory

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Sub Agents.directory

Powered by Claude · Grounded in docs

I know everything about Sub Agents.directory. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

About

Sub-Agents Directory is a curated collection of 100+ sub-agent prompts and MCP servers for Claude Code. Browse by category, search by keyword, or generate custom agents with AI.

Features

  • Searchable Directory — Find the right sub-agent for your task
  • Categorized Prompts — Language specialists, DevOps, Security, AI/ML, and more
  • MCP Server Registry — Extend Claude Code with external tools
  • AI Rule Generator — Create custom sub-agents tailored to your needs
  • One-Click Copy — Copy prompts directly to your clipboard
  • Open in Claude/ChatGPT — Use prompts instantly in your favorite AI assistant

Getting Started

# Clone the repository
git clone https://github.com/ayush-that/sub-agents.directory.git
cd sub-agents.directory

# Install dependencies
bun install

# Start the development server
bun dev

Open http://localhost:3000 to view the directory.

Contributing

We welcome contributions! To add a new sub-agent:

1. Fork & Clone

git clone https://github.com/YOUR_USERNAME/sub-agents.directory.git
cd sub-agents.directory
bun install

2. Create a Rule File

Add a new markdown file in the appropriate category folder:

content/
├── 01-core-development/
├── 02-language-specialists/
├── 03-infrastructure/
├── 04-quality-security/
├── 05-data-ai/
├── 06-developer-experience/
├── 07-specialized-domains/
├── 08-business-product/
├── 09-meta-orchestration/
└── 10-research-analysis/

3. Define Your Rule

Each rule follows this format:

---
name: your-agent-name
description: Brief description of what the agent does
tools: Read, Write, Edit, Bash, Glob, Grep
---

Your agent instructions go here...

4. Submit a PR

Open a pull request to this repository. We'll review and merge it!

Tech Stack

License

MIT

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About Sub Agents.directory

How do I install Sub Agents.directory?

Run npx sub-agents-directory, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Sub Agents.directory safe to use with an AI agent?

Its trust score is 72 out of 100 (good). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Sub Agents.directory still maintained?

The last commit was 6 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.