Best Claude Code agents
Specialized agents for Claude Code — architecture, review, testing, security, and domain expertise.
Specialized agents for Claude Code — architecture, review, testing, security, and domain expertise.
Compared at a glance
The top 5 picks side by side on trust, install, platform support, and disclosed notes — full rationale for each below.
| Field | Agent Observability SRE Agent Community reusable agent prompt for Claude Code analytics and agent platform on-call using official analytics documentation: usage signals, session failure triage, MCP latency patterns, and SRE runbooks for agent hosting teams. Open dossier | Agent View Fleet Operator Agent A reusable agent prompt for running a fleet of Claude Code background sessions from agent view (opened with the agents command). It triages which sessions need input, which are still working, and which have finished, then decides what to dispatch next, which to answer, and which to stop. Open dossier | Claude Code Desktop Operations Agent Community reusable agent prompt for operating Claude Code Desktop using official desktop docs: parallel sessions, agent view, notifications, background jobs, and desktop-specific troubleshooting workflows. Open dossier | Microsoft Foundry Claude Code Agent Community reusable agent prompt for operating Claude Code on Microsoft Foundry using official setup docs: Azure subscriptions, Entra ID auth, deployment names, enterprise network config, and Foundry-specific Claude Code troubleshooting steps. Open dossier | Agent Skill QA Reviewer Agent Source-backed Claude Code subagent prompt for reviewing Agent Skills before adoption or publication, checking SKILL.md scope, descriptions, invocation control, supporting files, tool permissions, helpfulness, safety, and privacy risks against official Claude Code skills guidance. Open dossier |
|---|---|---|---|---|---|
| Trust | |||||
| Install risk | Review first | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | agents | agents | agents | agents | agents |
| Source | source-backed | source-backed | source-backed | source-backed | source-backed |
| Author | kiannidev | JPette1783 | kiannidev | kiannidev | Desel72 |
| Added | 2026-06-16 | 2026-06-05 | 2026-06-16 | 2026-06-16 | 2026-06-08 |
| Platforms | Claude Code | Claude Code | Claude Code | Claude Code | Claude Code |
| Source repo | — | — | — | — | — |
| Safety notes | ✓Incident commands must not exfiltrate customer prompts into public tickets. Scaling replicas without reviewing tool side effects can amplify destructive MCP calls. Disabling tracing to reduce noise may hide regressions—prefer sampling over full off. Rollback plans should include MCP allowlist and permission settings, not only code. | ✓This agent prioritizes and routes attention across sessions; it does not bypass each session's own permissions. Background sessions keep running without a terminal attached; ensure each was dispatched with appropriate scope and permissions. Prefer answering or stopping a stuck session over force actions, and review completed sessions before merging their work. | ✓Parallel desktop sessions on the same branch can race—use worktrees or separate branches. Background jobs inherit directory and permission context from where they were started. Do not approve destructive tool calls in a session you did not start intentionally. | ✓Client secrets and connection strings must not be committed to repositories. Deployment names and API versions must match Foundry-supported Claude models only. Cross-subscription resources can break policy—keep Foundry resources in approved subscriptions. Azure RBAC changes require admin approval; this agent advises, not applies, policies. | ✓This agent reviews skill quality and adoption readiness; it does not execute the skill, install plugins, run scripts, or approve production rollout by itself. Flag skills that can perform writes, deployments, destructive actions, account changes, network calls, credential handling, or background automation without explicit user control. Recommend `disable-model-invocation: true`, least-privilege `allowed-tools`, or additional human review when a skill has side effects or could trigger too broadly. Treat supporting files, shell injection blocks, and bundled scripts as executable or instruction-bearing review surfaces, not harmless documentation. |
| Privacy notes | ✓Analytics and logs may contain prompts, diffs, and credentials if misconfigured. Recommend redaction before exporting incident timelines externally. Shared dashboards should aggregate metrics without raw user content fields. | ✓Agent view shows live session activity and working directories; restrict who can view and dispatch sessions. Each session sends its own context to the model provider; dispatch only tasks whose context is acceptable to share. Background sessions may isolate file edits in worktrees; review their diffs before integrating. | ✓Desktop session titles and diffs may expose proprietary code during screen sharing. Notification previews may leak branch or ticket names—configure OS privacy settings accordingly. Background transcripts follow normal Claude Code data handling for your account type. | ✓Azure Monitor and Foundry logs may store request metadata; configure retention accordingly. Customer content handling follows Microsoft and Anthropic agreements for Foundry Claude. Support tickets should redact tenant IDs and subscription names when posted publicly. | ✓Reads local skill instructions and supporting files, which may expose internal workflow names, repository paths, policies, examples, customer data, or credentials accidentally written into prompts. Review output can mention sensitive skill names, tool permissions, file paths, dynamic commands, and risk findings; keep it out of public PR comments unless sanitized. Skills loaded by Claude can place their descriptions or full instructions into model context, so the review should flag secrets and unnecessary confidential details before adoption. |
| Prerequisites |
|
|
|
|
|
| Install | — | — | — | — | — |
| Config | — | — | — | — | — |
| Citations | |||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
- 01Why it made the cut
Agent Observability SRE Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 02Why it made the cut
Agent View Fleet Operator Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 03Why it made the cut
Claude Code Desktop Operations Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 04Why it made the cut
Microsoft Foundry Claude Code Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 05Why it made the cut
Agent Skill QA Reviewer Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 06Why it made the cut
Agent Skills Enterprise Librarian Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 07Why it made the cut
AI Agent Cost Governance Analyst Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 08Why it made the cut
Bedrock Claude Code Platform Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 09Why it made the cut
Claude Code Auto Mode Policy Auditor Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 10Why it made the cut
Claude Code Enterprise Rollout Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 11Why it made the cut
Claude Code Routine Designer Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 12Why it made the cut
Claude Code Security Guidance Remediator Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 13Why it made the cut
Claude Code Worktree Coordinator Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 14Why it made the cut
Claude Plugin Marketplace Reviewer Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 15Why it made the cut
Claude Slack Delegation Triage Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
- 16Why it made the cut
Computer Use GUI Test Agent is included because it has safety notes present, privacy notes present, source-backed source posture.
Reach for insteadIf this will touch credentials, local files, or production systems, inspect the upstream source first.
Missing a pick? Propose an edit to this list — every change goes through the same review queue as new entries.
Suggest a pickGet the weekly brief
One calm read on Claude workflows. Sundays. No tracking pixels.
Unsubscribe any time. No tracking pixels. No partner blasts.