Agents
Drop-in Claude Code subagents with focused system prompts — code review, debugging, architecture, and more.
Agents (subagents) are specialized Claude Code assistants, each with its own focused system prompt and isolated context window. Claude Code delegates matching work to them automatically, or you can invoke one explicitly. Every agent below is a plain Markdown file you can copy or download straight into ~/.claude/agents.
New here? Start with Getting Started with Claude Code Agents
Showing 1–24 of 84 results
Accessibility Auditor
Use this agent to audit web UI against WCAG 2.2 AA — semantics, keyboard, ARIA, contrast, forms, and motion. Examples — auditing a new component for keyboard traps, checking a form for accessible errors, running a pre-ship a11y pass on a page.
Agent Architect
Use this agent to design a new Claude Code subagent or review an existing one — scoping, description, toolset, model, and output contract. Examples — "design an agent that triages flaky tests", "review my code-reviewer agent for scope creep", "why won't Claude auto-delegate to my agent?".
Agent Reliability Reviewer
Use this agent to make an AI agent production-ready — reviewing its loops, cost controls, error handling, tool use, human-in-the-loop gates, checkpointing, and observability, then reporting concrete failure modes and fixes. Examples — "is our agent safe to ship?", "our agent loops forever / burns tokens, harden it", "add guardrails and recovery before we put this agent in front of users".
Agent Tool Integration Engineer
Use this agent to wire tools and function-calling into an agent loop reliably — clean tool schemas, errors fed back as observations, retries with limits, idempotency, and parallel calls. Examples — "connect our APIs as agent tools", "our agent calls tools wrong / ignores tool errors", "add function-calling with proper error recovery to our agent".
Analysis Reviewer
Use this agent to review a finished analysis for methodological errors before it ships — checking grain and double counting, join fan-out, rows silently dropped by filters and inner joins, sampling and truncation, null handling, time zone and date boundaries, numbers in the prose that disagree with the code's output, charts that mislead, and causal language resting on correlational evidence. Examples — 'review this notebook before I send the deck', 'the query and the summary disagree somewhere, find it', 'does this analysis actually support the conclusion it draws?'.
Annotation Evidence Reviewer
Review a supervised text-label adjudication packet for traceable excerpts, preserved independent responses and rule-supported resolutions; flag missing evidence without choosing final labels.
API Architect
Use this agent to design APIs — resource modeling, versioning, pagination, error contracts, REST vs GraphQL. Examples — designing a public API, reviewing an API spec, planning a breaking change.
Backend Developer
Use this agent to build server-side features — endpoints, business logic, data access, background jobs. Examples — a new REST/GraphQL endpoint, a queue worker, a database integration.
Browser Agent Engineer
Use this agent to build, harden, or debug browser-automation agents — web tasks via Browser Use, Stagehand, Skyvern, or Playwright-based stacks. Examples: automate a portal workflow, make a flaky browser agent reliable, add verification and guardrails to web automation, choose between vision and DOM grounding.
C# Pro
Use this agent for modern C#/.NET 8+ — records, pattern matching, nullable reference types, correct async/await, LINQ, Span<T>, and source generators — plus ASP.NET Core and EF Core. Examples — building a minimal-API service, fixing an EF Core N+1 or tracking leak, hunting a deadlock from sync-over-async, or turning on nullable reference types across a project.
Caption Reviewer
Review supplied caption text, timing and human listening notes against a named media version. Flag uncertain words, speaker/sound omissions and timing conflicts in an issue ledger; never claim to hear inaccessible audio, rewrite the source media or certify accessibility compliance.
CI/CD Engineer
Use this agent to design, speed up, and harden CI/CD pipelines on any provider (GitHub Actions, GitLab CI, CircleCI, Buildkite). Examples — setting up a build→test→deploy pipeline from scratch, cutting a 25-minute CI run down with caching and matrix parallelism, adding a canary or blue-green deploy with automatic rollback, or reviewing a workflow for leaked secrets, over-broad tokens, and unpinned third-party actions.
CLI Tooling Engineer
Use this agent to design or build a command-line tool — subcommand and flag layout, --help and error UX, exit codes, --json/machine output, config precedence, stdin/stdout/stderr and pipe behavior, TTY/color/NO_COLOR detection, and CLI testing. Examples — "design the command and flag surface for our new deploy CLI", "this tool prints errors to stdout and returns 0 on failure — fix its ergonomics", "make our command pipe-friendly and add a --json mode for CI".
Cloud Architect
Use this agent to design a cloud architecture on AWS, GCP, or Azure — compute, networking, data stores, IAM, and cost trade-offs. Examples — choosing serverless vs containers for a new service, designing a multi-account network boundary, picking a database and estimating its monthly cost.
Code Reviewer
Use this agent to review code changes for correctness, security, and maintainability before merging. Examples — reviewing a PR diff, auditing a new module, checking a refactor for regressions.
Content Editor
Use this agent to edit marketing and editorial drafts (blog posts, landing pages, emails, social copy, newsletters) for clarity and brand voice while marking every unsourced claim, statistic, and superlative with a [CITATION NEEDED] or [VERIFY] tag and a one-line reason, never inventing a source, and returning the edited draft with a change log. Examples — 'edit this post before it goes to the client', 'tighten this launch email and tell me which numbers I need to back up', 'check this page copy against brand-voice.md and mark anything we cannot prove'.
Context Engineer
Use this agent to engineer what an LLM agent carries in its context window — deciding what to include vs exclude vs retrieve on demand, designing project/agent memory (CLAUDE.md), compacting growing history, and allocating the token budget across system prompt, memory, retrieved docs, tool results, and conversation. Examples — "my agent forgets the schema we agreed on three turns ago", "the agent gets dumber and more inconsistent as the chat grows", "we're burning 60k tokens of tool output every turn", "what should this support agent always know vs look up?".
Contract Obligation Reviewer
Compare a prepared vendor-contract obligation register with supplied agreement and amendment text: flag missing qualifying language, unsupported dates or parties, unresolved cross-references, and unproven supersession. Return a source-linked review packet for qualified counsel; do not give legal conclusions or approve terms.
Data Engineer
Use this agent to build and maintain data pipelines — ingestion, ELT/ETL, warehouse modeling, orchestration, and data-quality tests. Examples — building an idempotent ingestion job, modeling a fact/dimension table in dbt, writing a safe backfill for a changed schema.
Data Scientist
Use this agent for data analysis — exploration, statistics, SQL, and clear findings. Examples — analyzing a dataset, writing an analytical SQL query, summarizing experiment results.
Database Architect
Use this agent to design data models and storage strategy from access patterns — schema design, normalization vs deliberate denormalization, relational vs document vs key-value vs wide-column vs graph selection, indexing, partitioning/sharding, transaction boundaries, and consistency models. Examples — modeling a new feature's schema, choosing a database for a write-heavy event workload, reviewing a schema for missing indexes or scaling cliffs, planning how to shard a table that no longer fits one node.
Debugger
Use this agent to diagnose failing tests, runtime errors, or unexpected behavior by forming and testing hypotheses. Examples — a stack trace to root-cause, a flaky test, a "works locally but not in CI" bug.
Dependency Manager
Use this agent to upgrade project dependencies safely — batching low-risk bumps apart from breaking majors and verifying each step. Examples — clearing months of stale packages, taking a single major version with migration notes, resolving a peer-dependency conflict.
Design Systems Librarian
Use this agent to keep a design system's tokens, components, and documentation consistent with each other — finding hardcoded colors, spacing, and radii that should be tokens, components with no docs and docs describing variants that no longer exist, naming drift between token names, component names, and design-tool variables, and stale documentation — then reporting the drift with severity and a prioritized fix list. Examples — 'audit our design system for hardcoded values', 'which components are undocumented or documented wrong?', 'our token names and the Figma variables have diverged, show me where'.
Frequently asked questions
- What is a Claude Code agent?
- A Claude Code agent (or subagent) is a specialized assistant defined by a Markdown file with a focused system prompt and its own isolated context window. Claude Code delegates matching tasks to it automatically, or you can invoke it by name.
- How do I install an agent?
- Copy or download the agent's Markdown file to ~/.claude/agents/<name>.md for all your projects, or .claude/agents/<name>.md inside a single project. Claude Code picks it up automatically — no restart required.
- Are these agents free?
- Yes. Every agent on AgentsCamp is free to copy, download, and use. They are open Markdown files with no signup or API key required.
- When should I use an agent instead of a skill or slash command?
- Use an agent when you want delegated, multi-step work to run in its own context window, such as a code review or a debugging pass. Use a skill for on-demand expertise loaded into the main conversation, and a slash command for a quick reusable prompt you trigger with /name.
- Do these agents work outside Claude Code?
- Agents follow Claude Code's subagent file format, so they install directly into Claude Code. The system prompts inside them can also be adapted for other agent frameworks.