Browse the documentation

Roster of all 48 agents

Every BMAD+ agent in one place: 15 entry points, 6 Dev Studio personas and 27 Shield specialists, with their pack, role and how to call them, each linked to its pack page.

On this page
  1. The 15 entry points
  2. The 6 Dev Studio personas
  3. The 27 Shield specialists

BMAD+ 0.23.0 ships 48 agents. An agent is a named persona with written instructions and a menu of capabilities; your AI coding tool loads it and you call it by name. The count breaks down into 15 entry points (the agents the installer places and the ones you normally address), 6 Dev Studio personas that the Dev Studio orchestrator routes to, and 27 Shield specialists that the Shield orchestrator routes to. Only the packs you install are present in your project: the list below is the full catalogue.

Note Why the generated roster shows fewer lines

The roster in a project’s AGENTS.md lists 20 lines: the 14 entry points plus the six Dev Studio personas. The Dev Studio orchestrator has no line of its own there, and Shield appears once with its specialists behind it. This page counts every agent file, which gives 48.

The 15 entry points

Entry-point agents, by pack
AgentPackRoleHow to call
AtlasCoreStrategist: business analysis and product managementAtlas, <task>
ForgeCoreArchitect-Dev: architecture, development, documentationForge, <task>
SentinelCoreQuality: QA, UX review, human acceptance (recette)Sentinel, <task>
NexusCoreOrchestrator: sprints, autopilot, parallel supervisionNexus, <task>, autopilot, parallel
ShadowOSINTOSINT analyst: governed public-source researchShadow, <task>
MakerMakerAgent creator: design, validate and package new agentsMaker, <task>
ShieldShieldGRC orchestrator: routes to 27 specialists and 11 workflowsShield, <task or framework>
SEO ScoutSEO / GEOTechnical scanner: crawling, technical inspection, screenshotsSEO Scout, <task>, SEO Scout, run a technical audit of <url>
SEO ChiefSEO / GEOStrategist and reporter: scoring, plans, reports, benchmarksSEO Chief, <task>, SEO Chief, build a plan for <type>
SEO JudgeSEO / GEOContent and AI analyst: E-E-A-T, structured data, GEOSEO Judge, <task>, SEO Judge, check the structured data of <url>
ZecherMemoryMemory archivist: consolidation, project scan, context recall, handoffsZecher, <task>
Dev Studio OrchestratorDev StudioRoutes a task to one of six personas and 38 workflows<persona>, use <workflow-id> …
Backup ManagerBackupBackup and restore: timestamped ZIPs, rotation/backup, /backup-list, /backup-restore, /backup-clean
Animated Website CreatorAnimatedWebsite builder: MP4 to scroll-driven pageAnimated Website Creator, <task>, animated website from hero.mp4
AtelierDesignDesign engine: build, audit and redesign interfacesAtelier, <task>, /design read

Replace <task> with a plain sentence. The SEO agents answer to plain requests such as the ones in the table; their skill also routes /seo command words typed in the chat, which are not slash commands registered by your tool. Atelier understands /design read in the same way, and the Backup Manager works from the four commands in its menu. Every agent accepts its name followed by a request, a menu code or a menu line; the activation page explains how.

The 6 Dev Studio personas

Dev Studio personas
PersonaRoleHow to call
Miriam (מרים)Business Analyst: strategic analysis, research, product briefsMiriam, use product-brief …
Huldah (חולדה)Technical Writer: documentation, diagrams, editorial reviewHuldah, run document-project …
Yosef (יוסף)Product Manager: PRD, requirements, prioritisationYosef, validate-prd on …
Rachel (רחל)UX Designer: user experience, wireframes, empathy mappingRachel, create-ux-design for …
Bezalel (בצלאל)System Architect: architecture, decision records, epics and storiesBezalel, design the architecture …
Oholiab (אהליאב)Senior Engineer: TDD, sprint, code review, implementationOholiab, use investigate …

All six belong to the Dev Studio pack, which lists the 38 workflows each persona owns.

The 27 Shield specialists

Shield specialist agents
SpecialistFrameworkCategory
gdpr-agentGDPRData Privacy
ccpa-agentCCPA / CPRAData Privacy
lgpd-agentLGPDData Privacy
dpdpa-agentDPDPAData Privacy
iso27701-agentISO/IEC 27701Data Privacy
iso27001-agentISO/IEC 27001Cybersecurity
nist-csf-agentNIST CSF 2.0Cybersecurity
nist-800-53-agentNIST SP 800-53 Rev. 5Cybersecurity
cis-controls-agentCIS Controls v8Cybersecurity
nis2-agentNIS2Cybersecurity
ism-agentAustralian ISMCybersecurity
soc2-agentSOC 2Industry Compliance
pci-dss-agentPCI DSS v4.0.1Industry Compliance
hipaa-agentHIPAAIndustry Compliance
swift-csp-agentSWIFT CSPIndustry Compliance
dora-agentDORAIndustry Compliance
fedramp-agentFedRAMPIndustry Compliance
cmmc-agentCMMC 2.0Defense & Export
itar-agentITARDefense & Export
ear-agentEARDefense & Export
tsa-agentTSA Security DirectivesDefense & Export
eu-ai-act-agentEU AI ActAI Governance
iso42001-agentISO/IEC 42001AI Governance
nist-ai-rmf-agentNIST AI RMF 1.0AI Governance
wcag-agentWCAG 2.2Accessibility & ESG
section508-agentSection 508Accessibility & ESG
csrd-agentCSRDAccessibility & ESG

You do not call a specialist directly: ask Shield with the framework or the situation, and the orchestrator routes the request. The Shield page describes what each specialist covers and the 11 GDPR and AI Act workflow agents that sit beside them.

Ask who should handle a task

Use it when you know the job but not the agent. The assistant answers from the roster in your project’s AGENTS.md.

In your AI assistant
I want to document an existing repository, then check it against ISO 27001. Which agents should I call, in which order?

What you should get A sensible answer names Forge (Tech Writer role) or Huldah from Dev Studio for the documentation, then Shield, which routes to iso27001-agent, for the gap analysis, and tells you if any of them is not installed in this project.

See also