THE AI TOOLKIT / AGENTS
Agents.
A clear role.
A reviewable brief.
Find reusable agent definitions for real project work. Inspect the role, expected output and review notes, then reuse an attributed definition where its licence allows it.
01 / START WITH THE JOB
What are you working on?
Explore a category, then refine your shortlist.
All categories are available in the filters.
BUILT BY UNDOMINATED
Evidence tools you can inspect.
Original source, MIT licence and complete downloads.
Each review names the checks performed and their limits.
- AI resource curator ↗
Review skills, agents and MCP servers against a concrete use case, with pinned identity, rights and runtime evidence.
- Comparison editor ↗
Edit model-comparison copy so ties, same-seller tiers and dropped requirements are not published as dominance.
- Evidence reviewer ↗
Independently challenge numerical claims using source identity, denominator reconstruction and repeatable calculations.
- Model migration planner ↗
Plan workload-specific model migrations while preserving required capabilities and defining observable rollback criteria.
- Pricing source reviewer ↗
Review a provider price feed before any rate is admitted, including units, currency, tiers and prose quotes that are not USD.
- Resource release verifier ↗
Independently verify packaged resources, clean installation and meaningful public availability after a release.
02 / THE SELECTION
Find a fit. Read the reasoning.
Alphabetical by default. Every match is shown.
Compare up to three before opening a full review.
Runtime, access and execution
Labels summarise reviewed source wording. A local process can still send data to external services. Read each review's prerequisites and permissions; these filters do not certify compatibility or enforce access.
101 of 101 selected definitions
Accessibility · github
Accessibility Expert
Guides web accessibility work through keyboard, focus, screen-reader, zoom and contrast checks, with developer examples and a structured review checklist.
Why we selected itOperating rules require an a11y pre-check before code, verification steps with edits, and rejecting requests that remove focus outlines or otherwise reduce access.
Weigh upThe definition can edit files and run commands; it is broader than an advisory accessibility audit.
Accessibility · github
Accessibility Runtime Tester
Exercises keyboard journeys, focus changes and form errors, then records reproducible accessibility findings and retest steps.
Why we selected itRequires observed runtime behaviour and explicitly rejects a Lighthouse pass as proof of accessibility.
Weigh upThe body expects browser automation but the original allowlist does not enable the preferred Chrome DevTools or Playwright MCP tools. Configure and allow those tools in a working copy first.
Architecture and decisions · github
Adr Generator
Turns a concrete architecture decision into a numbered ADR with context, alternatives, consequences and references, asking for missing decision inputs first.
Why we selected itIt will not start until title, context, decision, alternatives, and stakeholders are present, and it tells the agent to ask rather than invent those fields.
Weigh upThe /docs/adr/ path is ambiguous outside its expected project layout; choose an explicit repository-relative output directory before use.
Agent development · Affaan Mustafa
Agent evaluator
Produces evidence-linked qualitative feedback on an agent’s output across five rubric dimensions.
Why we selected itRequires evidence for high as well as low assessments and identifies concrete improvements.
Weigh upRubric scores are subjective reviews, not benchmark measurements or reliability probabilities. Adapt the example git pager placement to git --no-pager log; no automatic gate is established.
Agent development · VoltAgent
Agent Memory Curator
Maintains a confirmed agent memory store with dated facts, visible corrections and user-reviewed pruning proposals.
Why we selected itRequires confirming the existing store rather than creating a competing memory system, and forbids storing secrets.
Weigh upThe file is a curation procedure, not a memory database, recall service or cross-session hook installer.
Agent development · anthropics
Agent Sdk Verifier Ts
Checks a TypeScript Claude Agent SDK project against its configuration, current SDK guidance, type-checking results and environment-variable hygiene before a structured readiness report.
Why we selected itChecklist is SDK-specific: package name, "type":"module", engines, MCP/subagent/permissions patterns, ANTHROPIC_API_KEY in .env.example and .env gitignore.
Weigh upNo tool allowlist is declared, so documentation retrieval and shell execution use inherited host permissions.
Agent development · VoltAgent
Agent-Log Knowledge Synthesizer
Finds recurring patterns in an explicitly scoped set of agent logs and writes cited findings with counts derived from the actual files.
Why we selected itStops on an empty or unspecified source scope and distinguishes recurring evidence from a single unconfirmed anecdote.
Weigh upIt cannot run analytics jobs or query remote services with its declared file tools; inputs must be accessible files.
Security and governance · awslabs
AI-DLC Compliance Agent
Organizes data classification, requirement-to-control mapping and compliance evidence into an advisory role within an AI-DLC project.
Why we selected itConnects each proposed control to its technical implementation and required evidence such as logs, configuration and test results.
Weigh upRequires the AI-DLC framework, active-space policies and resolved knowledge references; the raw persona download is not a complete installation.
Architecture and decisions · Agency Agents
API Platform Engineer
Designs contract-first public APIs with a backward-compatibility check on every change, forcing breaking changes through versioning and a humane deprecation runway.
Why we selected itDefault requirement that every API change is checked against the contract for backward compatibility, with breaking changes routed through versioning and deprecation, never silent breaks.
Weigh upConvention choices (naming case, pagination style) are consistency mandates; adopting projects must pick and record their own standards.
Documentation and knowledge · wshobson
API Reference Builder
Builds a versioned API or configuration reference from an inventory of the implementation’s public interfaces.
Why we selected itUses a consistent entry format for signatures, defaults, required fields, errors and deprecations.
Weigh upExhaustive coverage is an instruction, not a guarantee. Check the output against a source inventory and execute important examples.
Architecture and decisions · anthropics
Architecture Critic
Challenges modernization designs and transformed code against actual requirements, failure paths and simpler alternatives, ending with prioritized actionable findings.
Why we selected itSeparate review lenses distinguish architecture proposals from already-transformed code.
Weigh upRead-only shell use is an instruction; Bash remains available and must be constrained by the host.
Operations and reliability · GitHub
AWS Incident Triage
Structures an AWS incident investigation from alarms and blast radius to a time-bounded root-cause hypothesis.
Why we selected itCorrelates metrics, logs, traces and recent changes instead of promoting a single alarm to a cause.
Weigh upThe definition has no explicit tool allowlist. Read-only intent is not a host permission boundary; phase timeboxes are prescribed workflow targets.
Modernization and specifications · anthropics
Business Rules Extractor
Extracts domain calculations, validation and policy rules from legacy code into concrete test scenarios with source references and uncertainty questions.
Why we selected itSeparates business rules from infrastructure behavior and requires exact code locations.
Weigh upObserved legacy behavior is not automatically the business behavior that should be retained.
Architecture and decisions · wshobson
C4 System Context Documenter
Synthesizes system and component documentation into a stakeholder-facing context diagram, actor list and external-dependency map.
Why we selected itDefines a full c4-context.md output covering system purpose, personas, features, journeys and external systems.
Weigh upAssumes container, component and system documentation are available; the file does not include those inputs or the other C4 agents.
Operations and reliability · GitHub community
Cloud and SaaS Outage Triage
Separates upstream cloud/SaaS incidents from application failures with a timestamped evidence snapshot before any code is changed.
Why we selected itRequires a timestamped dependency-health snapshot and separates confirmed facts, plausible hypotheses and unknowns before proposing code changes.
Weigh upRequires the OutageDeck MCP server (remote http) plus repository/log access; without it only the local-investigation half of the workflow runs.
Architecture and decisions · anthropics
Code Architect
Turns observed repository conventions into a concrete feature blueprint with file changes, interfaces, trade-offs and an implementation sequence.
Why we selected itRequires existing patterns and conventions to be supported by file-and-line references before proposing a design.
Weigh upThe prompt asks for one decisive design; use another review process when competing designs or unresolved requirements need comparison.
Codebase understanding · anthropics
Code Explorer
Traces an existing feature from entry points through state changes and storage, producing a source-linked map for the next developer.
Why we selected itRequires call-chain and data-transformation tracing, so the output goes beyond a directory summary.
Weigh upIt produces an explanatory map rather than implementing changes or proving behavior with executed tests.
Code maintenance · anthropics
Code Simplifier
Refines recently changed code for clearer structure and naming while explicitly keeping its behavior and scope intact.
Why we selected itLimits the default pass to code changed in the current session and explicitly prioritizes behavior preservation.
Weigh upIts embedded coding preferences target JavaScript, TypeScript and React; they need review against other languages and the project’s own conventions.
Codebase understanding · Agency Agents
Codebase Archaeologist
Audits codebases touched by many AI sessions for silent logic mismatches, dead code and doc-vs-code divergence, producing findings only.
Why we selected itExplicitly does not rewrite or refactor; it produces precise, evidenced, prioritized findings plus a maintained drift registry answering which files are safe to build on.
Weigh upThe file declares no tools allowlist; run it with host-default tools restricted to read-only, since the role is findings-only by instruction, not by enforcement.
Documentation and knowledge · GitHub community
CodeTour Guide Builder
Plans and writes guided code walkthroughs with file references and a maintenance checklist.
Why we selected itMaps learning objectives to concrete files and steps, with optional Git references for versioned context.
Weigh upSome embedded JSON blocks are illustrative fragments rather than complete tour files. Validate final output against the current CodeTour schema.
Documentation · anthropics
Comment Analyzer
Checks comments and docstrings against implementation behavior, then separates factual errors, worthwhile improvements and obsolete explanations.
Why we selected itExplicitly cross-checks signatures, side effects, error conditions and complexity claims against source code.
Weigh upThis is advisory review: the body explicitly forbids modifying code or comments.
Security and governance · 0xSteph
Compliance mapper
Maps documented security findings to scoped control gaps and evidence requirements.
Why we selected itRequires support for each mapping and separates a technical gap from a legal or audit conclusion.
Weigh upIt does not certify compliance or provide a legal conclusion. Standards text may have separate access/licence terms, and referenced shell helpers are not installed by this profile.
Security review · 0xSteph
Crypto Analyzer
Reviews cryptographic usage, key/nonce handling, TLS and token design within an authorized code review.
Why we selected itKeeps advisory analysis separate from active cracking or exploitation and checks contextual misuse rather than algorithm names alone.
Weigh upNo formal cryptographic assurance or active test is established. Referenced findings.sh integration needs separate tooling; Bash is not in this profile’s declared tools.
Data and analytics · wshobson/agents
Data Engineer
A broad design prompt for batch and streaming pipelines, data quality, schema evolution and operational handoffs.
Why we selected itCovers failure handling, incremental processing and schema evolution alongside the happy-path transformation.
Weigh upThe file supplies instructions, not an executable pipeline or verified expertise across every listed cloud and engine.
Security and privacy · Trail of Bits
Data Flow Analyzer
Traces a suspected vulnerability from sink to sources with trust levels and validation points, producing structured read-only evidence.
Why we selected itDeclares only Read, Grep and Glob and states read-only explicitly; the four-phase trace (sink, sources with trust levels, per-validation pass/fail/bypass, full path) is checkable line by line.
Weigh upDesigned as a Phase-1 worker for the fp-check skill; used standalone the caller must supply the bug description (claim, class, file:line, trigger, impact) as dispatch input.
3 sources · 2026-10-07
Read the full review Attributed definition availableCC-BY-SA-4.0Data and retrieval · wshobson
Database Cloud Optimization Database Optimizer
Investigates database bottlenecks from query plans and workload evidence, then proposes query, index, caching or partitioning changes with validation.
Why we selected itBehavioral trait “Measures performance first using appropriate profiling tools before making optimizations” is the right order for this role.
Weigh upThis is an implementation-capable role and it declares no tool allowlist; database credentials and migration authority must be scoped in the host.
Operations and reliability · Agency Agents
Database Reliability Engineer
Keeps stateful datastores available and recoverable with tested restores, drilled failovers and lock-budgeted online migrations, each carrying a written back-out plan.
Why we selected itPairs backfill and rollback rules explicitly: batched backfills kept out of exclusive-lock transactions, plus a written back-out plan and blast-radius estimate for every migration, failover and large delete.
Weigh upThe RPO and RTO figures in the template are illustrative targets, not guarantees; each project must set and then prove its own numbers with drills.
Data and retrieval · affaan-m
Database Reviewer
Reviews PostgreSQL queries, schemas and migrations for performance, integrity and Row Level Security, reporting findings only.
Why we selected itDeclares only Read, Grep, Glob and Bash (no Write/Edit), so the review-only posture is enforced by the tool list, not just by instruction.
Weigh upDiagnostic queries need a readable DATABASE_URL; the definition does not gate who may supply production credentials.
Documentation and knowledge · GitHub community
Demonstrate Understanding
Checks a developer’s understanding of a codebase through focused questions and evidence-backed feedback.
Why we selected itUses questions about actual implementation choices, edge cases and tradeoffs instead of immediately supplying a full explanation.
Weigh upThe agent can misunderstand code or a learner’s answer; verify feedback against source and tests.
Infrastructure and delivery · wshobson
Deploy with Verification
Runs test, build, deploy and live verification in order, and never reports shipped until the live system serves the new build.
Why we selected itHard rules stop on test failure and require live health/version confirmation reflecting the just-shipped revision, catching exit-0 deploys that keep serving the old build.
Weigh upTemplate placeholders (repo path, test/build/deploy commands, health endpoint, state doc) must be filled per project; unfilled it cannot run.
Security review · 0xSteph
Detection engineer
Drafts defensive detection rules and SIEM queries with telemetry requirements and tuning notes.
Why we selected itConnects rule logic to observable signals, likely false positives and an explicit test plan.
Weigh upGenerated Sigma/SPL/KQL/YARA or network signatures need actual parser and environment tests before deployment. No Bash tool is declared for referenced shell helpers.
Architecture and decisions · github
Devils Advocate
Stress-tests a proposal through one objection at a time, then switches to a balanced recap when the user ends the debate.
Why we selected itA clear dialogue protocol keeps each challenge focused and gives the user an explicit way to stop adversarial mode.
Weigh upIt deliberately challenges rather than neutrally weighs a proposal during debate; use the final recap to recover balance.
Browser and performance · github
Devtools Regression Investigator
Reproduces browser regressions and links screenshots, console or network evidence to likely code paths, returning a structured bug report before any requested fix.
Why we selected itThe file forbids declaring root cause without browser evidence or code correlation, and forbids treating a flaky repro as solved.
Weigh upChrome DevTools MCP and optional Playwright are described but not installed or explicitly named in the tool allowlist; configure the required browser tools separately.
Testing and review · affaan-m
Django Reviewer
Reviews Django changes for ORM, migration-safety, DRF, Celery and security pitfalls with severity-graded findings and merge-blocking approval criteria.
Why we selected itMigration-safety rules are rollback-aware: RunPython requires reverse code, column drops go two-phase across deployments, and every model change must carry a migration.
Weigh upReferenced companion skills such as django-patterns, django-security and django-tdd are not bundled with the standalone file; treat those pointers as optional.
Documentation · wshobson
Documentation Generation Docs Architect
Builds a structured architecture manual from an existing codebase, covering design rationale, component interactions, operational behavior and paths into the source.
Why we selected itOutput contract is specific: Markdown, heading hierarchy, code blocks, tables, links as file_path:line_number, 10-section skeleton.
Weigh upThe source favors extensive manuals; choose a bounded audience and scope to avoid documentation that is costly to maintain.
Operations and reliability · VoltAgent
Error Coordinator
Mines logs and agent output for recurring failure and cascade patterns, citing evidence paths and refusing to invent quantities.
Why we selected itRequires every reported count to be Grep/Glob-counted with path:line evidence, a two-independent-source minimum for patterns, and explicitly forbids reporting recovery rates, MTTR or cascades prevented.
Weigh upNo Bash tool is declared, so mining is limited to what Read/Glob/Grep can see; live detection, retries and circuit-breaking are explicitly out of scope.
Architecture and decisions · wshobson
Event Sourcing Architect
Plans event-sourced systems through aggregate boundaries, immutable event records, projections, sagas and event-versioning decisions.
Why we selected itCovers the practical linkage between command handling, read projections and cross-aggregate workflows.
Weigh upThe role assumes event sourcing is appropriate; it does not compare simpler persistence designs first.
Testing and review · affaan-m
FastAPI Reviewer
Reviews FastAPI changes for async blocking, dependency wiring, schema exposure and test setup, with file references and explicit unverified risks.
Why we selected itFocuses on framework-specific failure modes such as blocking clients in async routes, incorrect test overrides and sensitive response fields.
Weigh upIts severity checklist includes architectural preferences that require context; an inline database session is not automatically a demonstrated vulnerability.
Research and product · msitarzewski
Feedback Synthesizer
Organizes a supplied customer-feedback corpus into themes, product priorities and audience-specific reports for product and support teams.
Why we selected itSpecifies separate executive, product-team and customer-success deliverables rather than one undifferentiated summary.
Weigh upThe definition's accuracy, growth and service-level targets are aspirations; none were demonstrated by this source review.
Security review · 0xSteph
Fix Verifier
Retests an authorized vulnerability fix against the original case, root-cause variants and legitimate behavior.
Why we selected itUses explicit outcomes for partial fixes, regressions and unverifiable cases rather than forcing closure.
Weigh upA retest can mutate a service even when intended as non-destructive. Findings helpers and live target behavior were not exercised in this source review.
Browser and performance · github
Frontend Performance Investigator
Diagnoses a specific slow web flow from traces, network activity and code paths, then produces prioritized fixes with a validation method for each.
Why we selected itRequires a concrete reproduction path and recorded environment assumptions before recommending optimizations.
Weigh upChrome DevTools MCP and the optional Playwright fallback require separate configuration; neither is explicitly included in this file’s tool allowlist.
Codebase understanding · Trail of Bits (Omar Inuwa)
Function Analyzer
Builds a line-cited account of one function’s invariants, assumptions and callee dependencies before a later security review.
Why we selected itRequires reading callees and their branches before treating a precondition as enforced; function names are explicitly insufficient evidence.
Weigh upThe file requires sibling analysis formats and domain references plus a resolved {baseDir}; the download alone does not install the plugin.
6 sources · 2026-09-21
Read the full review Attributed definition availableCC-BY-SA-4.0Infrastructure and delivery · github
Github Actions Expert
Designs and reviews GitHub Actions workflows around minimal token permissions, immutable action references, OIDC, deployment concurrency and validation.
Why we selected itAction pinning section forbids `@main`/`@latest`/moving tags, requires full commit SHA plus a version comment, and explains tag-move supply-chain risk.
Weigh upThe GitHub tool wildcard and terminal access can perform repository actions; the definition itself does not enforce a read-only review.
Documentation editing · GitHub
GitHub Docs readability editor
Guides a readability pass over assigned Markdown files while preserving meaning, qualifiers and essential technical details.
Why we selected itEdits are limited to the specific markdown files provided. The file says not to move or delete files, and to keep the original sentence when an edit would change its meaning.
Weigh upThe body restricts editing to assigned Markdown files, but this is an instruction rather than an enforced filesystem boundary. Frontmatter includes edit, search, web, github/* and execute.
Agent development · affaan-m
Harness Optimizer
Tunes agent configuration with an explicit evaluation definition, repeated trials, baseline checks and rollback instructions for failed experiments.
Why we selected itExplicit non-goals: no product-code rewrites; no slash-command invocation; run node scripts/harness-audit.js instead.
Weigh upRequires the upstream-style scripts/harness-audit.js, tests/run-all.js and skills/eval-harness/SKILL.md; a standalone download cannot run that workflow by itself.
Testing and review · wshobson
Hypothesis Debugging Investigator
Investigates one assigned bug hypothesis and sends the team lead a cited account of supporting evidence, contradictions and remaining gaps.
Why we selected itDefines confirmation, falsification and ambiguous evidence before investigation, reducing one-sided hypothesis confirmation.
Weigh upDepends on a lead and the host’s messaging/task tools. The single file does not create a team or an orchestration workflow.
Operations and reliability · Seth Hobson
Incident Responder
Organizes incident command, stabilization, communication and post-incident follow-up.
Why we selected itSeparates immediate mitigation from root-cause work and assigns operational/communication responsibilities.
Weigh upIts response-time targets are example policies, not service guarantees. No tool allowlist enforces read-only behavior; external communication and production mutations need explicit operational authority.
Research and product · github
Jobs-to-be-Done UX Planner
Turns user context and jobs to be done into a journey map, flow specification and design handoff documents.
Why we selected itStarts by asking about users, context and pain points instead of treating a requested interface feature as the underlying goal.
Weigh upThe agent drafts research artifacts; it does not conduct interviews, validate personas or create Figma designs.
Codebase understanding · anthropics
Legacy Analyst
Builds an evidence-linked account of an unfamiliar legacy system by tracing entry points, stable data structures and actual control flow.
Why we selected itRequires source citations and explicitly distinguishes observed behavior from inferred intent.
Weigh upThe role is an analyst, not a migration implementer or an executable behavior test.
Model evaluation · Seth Hobson
LLM Fine-Tuning Eval Engineer
Separates fine-tuning evaluation and checkpoint promotion review from the training operator.
Why we selected itRequires calibrated graders, pinned baselines and leakage checks before relying on candidate improvements.
Weigh upPrescribed sample sizes are heuristics, not powered-study guarantees. The role omits a tool allowlist, and companion skills/training infrastructure are not installed by this profile.
Accessibility · github
Markdown Accessibility Assistant
Reviews existing Markdown for accessible headings, links, lists and image descriptions, while reserving meaning-changing rewrites for human approval.
Why we selected itMission forbids generating docs from scratch and limits work to improving existing markdown, which is a real role boundary.
Weigh upThe scope is selected Markdown accessibility practices, not full web accessibility conformance.
Model evaluation · Affaan Mustafa
MLE Reviewer
Reviews ML engineering changes for data contracts, leakage, reproducibility and serving regressions.
Why we selected itChecks time/entity splits and training-serving feature consistency with concrete file-level evidence.
Weigh upBash is not a read-only sandbox. The source forbids unapproved dependency installation; model quality and production behavior remain unmeasured by this catalogue review.
Operations and reliability · Agency Agents
Mobile Release Engineer
Engineers the signing-to-store path for iOS and Android with phased rollouts and a forward-fix-only recovery model, since shipped binaries cannot be rolled back.
Why we selected itStates the no-rollback constraint explicitly and requires phased rollouts with pre-defined halt-on-crash-spike thresholds plus a forward-fix path before shipping.
Weigh upFastlane, match or secrets-manager storage, store accounts and CI runners must be configured in the host project; the file supplies the workflow, not credentials.
Data and retrieval · github
MongoDB Performance Advisor
Combines repository query patterns with read-only MongoDB diagnostics to explain query plans and index trade-offs.
Why we selected itStops when a read-only MongoDB MCP connection is unavailable instead of fabricating database observations.
Weigh upRequires the MongoDB MCP server configured read-only; Atlas Performance Advisor also needs the appropriate account access.
Modernization and specifications · github
Neon Migration Specialist
Tests schema changes on a temporary Neon database branch and prepares migration files for a separate production rollout.
Why we selected itExplicitly forbids running migrations on the main Neon database branch and separates database branches from Git branches.
Weigh upWorkflow adjustment is required: the description promises automated production application and zero downtime, while the body prohibits main-branch migrations. Use only the test-branch workflow, with no downtime guarantee.
Operations and reliability · wshobson/agents
Observability Engineer
A planning prompt for telemetry coverage, service objectives, alert design and incident runbooks.
Why we selected itConnects metrics, logs and traces with service-level indicators and actionable incident response.
Weigh upThis is a broad instruction profile, not an installed collector, dashboard, integration or compliance control.
Modernization and specifications · anthropics
Pilot-Driven Uplift Migrator
Applies a proven version-upgrade playbook to one module, keeping edits within that unit and reporting its actual build result and playbook gaps.
Why we selected itStops without editing when the pilot playbook is missing, preventing a worker from improvising an untested migration approach.
Weigh upRequires a completed pilot, analysis/<system>/PLAYBOOK.md, DELTA_CATALOG.md and a designated module in the modernization working copy.
Operations and reliability · GitHub
Platform SRE for Kubernetes
Plans Kubernetes configuration and rollout work with rollback and operational verification.
Why we selected itRequires manifest checks and rollout observation and carries security/resource defaults into implementation.
Weigh upTool identifiers are host-specific and need adaptation. Replica counts, probes and deployment policies are examples; no cluster action or workload validation occurred here.
Testing and review · github
Playwright Test Explorer
Explores a working interface through Playwright before generating and running TypeScript tests for its observed user flows.
Why we selected itProhibits writing test code until the agent has navigated the interface and identified its actual flows.
Weigh upRequires a configured Playwright MCP connection and a reachable application; the file does not install a browser server or the test framework.
Security and governance · wshobson
Policy Enforcer
Authors, audits and explains Cedar policies that govern what an AI agent's tools may do, starting from allow-listed safe defaults.
Why we selected itTeaches Cedar evaluation semantics (deny authoritative, permit matching, context.input shapes per tool) instead of asserting protection from string filtering.
Weigh upThe file declares no tools allowlist, so enforce least privilege in the host; the role writes policy files and needs scoped Write.
Testing and review · anthropics
Pull Request Test Analyzer
Maps a pull request to its tests and identifies meaningful missing failure cases, brittle assertions and uncovered behavioral contracts.
Why we selected itPrioritizes tests by concrete regressions they would prevent rather than chasing line coverage.
Weigh upIts internal numerical criticality rubric is a prioritization instruction, not a measured quality score or a catalogue rating.
Data and analytics · GitHub community
PySpark Expert Agent
Reviews PySpark pipeline code for distributed-execution anti-patterns with confidence-graded hypotheses, Spark-native fixes, and a ban on inventing runtime evidence.
Why we selected itEvidence discipline is explicit: it must not invent Spark UI metrics or runtime evidence, and must ask for the minimum evidence such as explain output, stage symptoms, sizing and AQE state needed to confirm.
Weigh upStatic heuristics without cluster evidence stay hypotheses; confirm Medium and Low confidence findings against explain plans and the Spark UI before acting.
Data and analytics · GitHub community
Python Notebook Sample Builder
Builds a new Python demonstration notebook from snippets checked in the selected development environment.
Why we selected itAsks for snippets to be executed before they are placed in the notebook.
Weigh upThe prompt assumes a development container and broad package-install permissions; do not apply that assumption to an arbitrary host.
Testing and review · github
QA Test Planner and Investigator
Builds a requirement-linked test plan, explores failure paths and reports reproducible bugs separately from potential improvements.
Why we selected itOrganizes tests by boundary, negative, failure, concurrency and security cases, then prioritizes by risk.
Weigh upIt grants broad edit, execute, delegation and web tool categories; the role’s focus is not a technical read-only restriction.
Data and retrieval · affaan-m
Rag Pipeline Reviewer
Reviews retrieval pipelines for grounding, pruning, fallback behavior and evaluation policy, returning a structured approval, conditional approval or block decision.
Why we selected itRole boundary is negative as well as positive: do not rewrite the LLM answer prompt; hand off to named specialists.
Weigh upThe read-only Bash rule is an instruction; the host must enforce the intended access boundary.
Documentation · VoltAgent
Readme Generator
Builds a repository README from inspected manifests, scripts, tests and entry points, explicitly rejecting guessed commands, APIs and configuration.
Why we selected itRequires setup commands, configuration and usage examples to be extracted from actual repository evidence.
Weigh upThe opening context-manager request assumes a coordinator not supplied by the standalone file. Provide the repository purpose and audience directly when using it alone.
Model evaluation · GitHub
Research Harness Engineer
Builds research evaluation harnesses with null controls, separated calibration and held-out evidence.
Why we selected itRequires baseline reproduction before an improvement campaign and preserves metrics artifacts before narrative claims.
Weigh upA confidence interval crossing zero is inconclusive, not proof of no effect. Its forceful non-reproduction wording must not become an unsupported universal absence claim.
Research and product · msitarzewski
Research Synthesist
Builds an auditable synthesis that traces repeated claims to their origin and separates independent agreement, disagreement and missing evidence.
Why we selected itExplicitly rejects counting repeated citations to one study as independent corroboration.
Weigh upThe original frontmatter name and hex color need adaptation to the current Claude Code field rules before loading a working copy.
Modernization and specifications · anthropics
Scaffolder
Creates one modernization service from an approved architecture and specification, including its domain model, API stubs and rule-linked acceptance tests.
Why we selected itLimits the intended work to one caller-selected service directory so independently scaffolded services do not overwrite one another.
Weigh upRequires REIMAGINED_ARCHITECTURE.md, AI_NATIVE_SPEC.md and the caller’s modernized service path; the complete modernization workflow is not included.
Security and governance · github
Se: Responsible Ai
Screens user-facing changes for accessibility, privacy and exclusion concerns, then documents decisions and escalation needs in numbered responsible-AI records.
Why we selected itStep 2–4 give concrete tests: culturally varied names/ages/edge strings, keyboard vs clickable div, alt text, minimal vs excessive data collection, unbundled consent.
Weigh upThe illustrative name and demographic examples are screening prompts, not validated fairness tests or a compliance assessment.
Documentation · github
Se: Tech Writer
Turns code and design context into audience-specific documentation, tutorials, articles and decision records using explicit structures and a verification checklist.
Why we selected itContent-type templates are fully specified, including ADR status/deciders/consequences/alternatives and task-oriented user-guide workflows with verification checkpoints.
Weigh upThe frontmatter permits file editing and web retrieval but does not name an execution tool; testing or compiling examples needs a separate runner.
Accessibility · Agency Agents
Section 508 Accessibility Specialist
Audits and remediates web accessibility against the correct legal baseline (508 equals WCAG 2.0 AA) with assistive-technology testing, and reports honest VPAT conformance.
Why we selected itWCAG criterion references were screened against current W3C text with no misidentification found, including 1.3.1 Info and Relationships (A) and the 4.5:1 and 3:1 contrast thresholds, unlike the excluded a11y-architect's 2.4.11 error.
Weigh upThe 30 to 40 percent automated-tool coverage figures are the author's estimates, not independently measured here; treat them as cautionary guidance.
Security and governance · anthropics
Security Auditor
Reviews application code with a stack-specific security checklist, requiring source locations, exploit scenarios, concrete remediation and masked secrets in each finding.
Why we selected itDemands a plausible exploit scenario and a concrete code-level fix rather than unsupported vulnerability labels.
Weigh upBash and package auditors depend on host permissions and tool availability; the definition does not enforce its read-only boundary.
Data and analytics · Agency Agents
Spatial Data Engineer
A geospatial ETL planning prompt centered on source preservation, explicit coordinate systems and transformation checks.
Why we selected itRequires original files to be preserved and transformations to write to a new location.
Weigh upThe original frontmatter name contains spaces. Create a host-valid name in your working copy; this download remains byte-identical to upstream.
Modernization and specifications · affaan-m
Spec Miner
Extracts a selected brownfield capability into source-linked OpenSpec requirements and invariants while limiting writes to the specification directory.
Why we selected itWrite may only create openspec/specs/<capability>/spec.md; Bash must stay read-only—rare path-scoped reviewer-writer.
Weigh upIts output is tailored to OpenSpec; a different specification workflow requires adaptation.
Documentation and knowledge · GitHub community
Specification Writer
Develops implementation specifications with explicit requirements, interfaces, constraints and acceptance examples.
Why we selected itProvides structured sections for requirements, interfaces, dependencies and validation.
Weigh upGenerated requirements and examples still need stakeholder and implementation review; no executable conformance checker is bundled.
Testing and review · Trail of Bits (Omar Inuwa)
Specification-to-Code Checker
Checks one quoted requirement against its implementation paths and records the enforcement evidence, gaps and unresolved questions.
Why we selected itSeparates implemented, partially enforced, contradicted, absent, stronger-than-specified and undecidable requirements instead of forcing a binary pass/fail.
Weigh upThe file requires the plugin’s sibling analysis format and domain references; {baseDir} must resolve before use.
6 sources · 2026-09-21
Read the full review Attributed definition availableCC-BY-SA-4.0Data and analytics · wshobson/agents
SQL Pro
A SQL review prompt covering query plans, schema design, indexing and read/write performance tradeoffs.
Why we selected itAsks for usage patterns and realistic data before treating an index or rewrite as an optimization.
Weigh upSQL features and tuning advice are not portable across all named engines. Supply the exact engine, version, schema and workload.
Research and product · msitarzewski
Study Design and Evidence Statistician
Examines the chain from research question and measurement to comparison, analysis and decision, making assumptions and uncertainty explicit.
Why we selected itSeparates descriptive, predictive and causal questions before choosing a study or interpreting a result.
Weigh upThe prompt does not supply data, a statistical runtime or a validated analysis package. Calculations require suitable tools and reproducible inputs.
Framework development · Svelte
Svelte File Editor
A focused Svelte editing prompt that consults current documentation and iterates with the Svelte MCP static checker.
Why we selected itSeparates Svelte component work into a focused agent context with relevant documentation.
Weigh upThis listing recommends the configured Svelte MCP path. The prompt’s fallback CLI and normalized tool-name variants were not runtime-tested; map names to the tools your host actually exposes.
Testing and review · github
Systematic Debugging
Reproduces an application bug, tests root-cause hypotheses and verifies a minimal fix against the original failure.
Why we selected itRequires reproduction and an expected-versus-actual report before changing code.
Weigh upThe procedure is a general debugging framework, so the caller must provide a concrete symptom and a usable reproduction environment.
Testing and reliability · GitHub community
TDD Green Phase
Implements the smallest behavior change needed to satisfy an existing failing test.
Why we selected itStarts from an observed failing test and calls for the relevant suite after the change.
Weigh upGreen tests demonstrate only the asserted examples; hidden requirements and untested behavior still need review.
Testing and reliability · GitHub community
TDD Red Phase
Writes a failing test tied to a requirement before implementation work begins.
Why we selected itMaps the behavior to an explicit issue requirement and requires a test that fails for the intended reason.
Weigh upAn issue number inferred from a branch name must be verified against the intended repository and issue.
Testing and reliability · GitHub community
TDD Refactor Phase
Improves a tested implementation through small changes while preserving the existing behavior checks.
Why we selected itRequires green tests before and after each refactoring step.
Weigh upSecurity suggestions and passing tests are not a security audit or proof of behavioral equivalence.
Research and product · github
Technical Spike Research Mode
Investigates a supplied technical-spike document through cited documentation, repository examples and separately approved experiments, recording findings and dead ends as work proceeds.
Why we selected itStops when no spike document is provided and ties the work to explicit research questions and success criteria.
Weigh upThe recursive research policy has no fixed time or cost budget; define a stopping condition for the chosen spike.
Documentation · Agency Agents
Technical Writer
Writes developer documentation with a tested-snippet rule and docs-as-code pipeline guidance, so examples and versioned docs stay runnable instead of drifting.
Why we selected itRequires every code example to be tested before it ships and docs to match the software version they describe, deprecating rather than deleting old docs.
Weigh upThe 5-second, 30-second and 15-minute usability bars are author heuristics, not measured outcomes; treat them as editorial guidance.
Infrastructure and delivery · github
Terraform Iac Reviewer
Reviews and drafts Terraform changes with a plan summary, impact assessment, validation sequence, approval before apply, and an explicit recovery discussion.
Why we selected itEvery change must include plan summary (add/change/destroy counts), risk assessment, validation commands, and a rollback strategy.
Weigh upTerminal and editing access can change infrastructure. Approval before apply is an instruction, not an enforced host permission boundary.
Infrastructure and delivery · github
Terratest Module Testing
Designs Terraform module tests around outputs, validation failures and isolated setup and cleanup, with cloud applies explicitly gated.
Why we selected itDistinguishes success paths, expected failures and staged integration tests rather than treating every module test as a deployment.
Weigh upThe original tool list declares only legacy codebase and terminalCommand aliases. Map them to current read/search/execute tools and explicitly add an editor for writing tests; verify its pinned model is available.
Testing and review · anthropics
Test Engineer
Writes characterization tests and dual-run harnesses that pin legacy behavior before modernization, preserving unresolved target behavior as explicitly pending tests.
Why we selected itThe body pins tests to literal inputs/outputs and dual-run comparison against legacy or a recorded trace, not to spec-as-intent.
Weigh upFrontmatter grants Write, Edit, and unrestricted Bash; the modernized/-only and never-edit-legacy/ rules are prompt text, not a sandbox.
Security and governance · wshobson
Threat Modeling Expert
Structures a security design review around trust boundaries, data flows, attack paths, mitigations and residual risks.
Why we selected itProvides a concrete sequence from scope and assets through STRIDE and attack trees to documented residual risk.
Weigh upThis is a design-review role, not a scanner, penetration test or compliance certificate.
Security and privacy · GitHub community
Trojan Skill Hunter
Reviews agent instructions, hooks and MCP configuration as untrusted text before installation.
Why we selected itDirects the reviewer to inspect contributed instructions without executing or installing the contribution.
Weigh upPrompt instructions cannot make a model immune to prompt injection or replace isolated tooling and least-privilege access.
Testing and review · anthropics
Type Design Analyzer
Reviews domain types by identifying their invariants, checking where those invariants are enforced, and weighing safer designs against complexity and compatibility.
Why we selected itFixed per-type report: invariants list, four rated axes with justification, Strengths, Concerns, Recommended Improvements.
Weigh upIts numerical design rubric is subjective guidance, not a measured quality score or compiler result.
Testing and review · affaan-m
TypeScript Reviewer
Reviews TypeScript/JavaScript diffs with merge-readiness, typecheck and lint gates first, reporting findings without rewriting code.
Why we selected itEstablishes review scope without hard-coding main, then stops and reports on red CI, merge conflicts, failed typecheck/lint or empty scope instead of reviewing blindly.
Weigh upRuns tsc/eslint via Bash; the project's own check commands execute, so sandbox or resource consequences belong to the host configuration.
Evidence review · Undominated.ai
Undominated · AI resource curator
Review skills, agents and MCP servers against a concrete use case, with pinned identity, rights and runtime evidence.
Why we selected itDefines a specialist role, required evidence, handoff contract and explicit limits on external actions.
Weigh upPortable profile; manually load or adapt to a native agent format. No automatic subagent registration or permission grants.
Evidence review · Undominated.ai
Undominated · Comparison editor
Edit model-comparison copy so ties, same-seller tiers and dropped requirements are not published as dominance.
Why we selected itDefines a specialist role, required evidence, handoff contract and explicit limits on external actions.
Weigh upPortable profile; manually load or adapt to a native agent format. No automatic subagent registration or permission grants.
Evidence review · Undominated.ai
Undominated · Evidence reviewer
Independently challenge numerical claims using source identity, denominator reconstruction and repeatable calculations.
Why we selected itDefines a specialist role, required evidence, handoff contract and explicit limits on external actions.
Weigh upPortable profile; manually load or adapt to a native agent format. No automatic subagent registration or permission grants.
Evidence review · Undominated.ai
Undominated · Model migration planner
Plan workload-specific model migrations while preserving required capabilities and defining observable rollback criteria.
Why we selected itDefines a specialist role, required evidence, handoff contract and explicit limits on external actions.
Weigh upPortable profile; manually load or adapt to a native agent format. No automatic subagent registration or permission grants.
Evidence review · Undominated.ai
Undominated · Pricing source reviewer
Review a provider price feed before any rate is admitted, including units, currency, tiers and prose quotes that are not USD.
Why we selected itDefines a specialist role, required evidence, handoff contract and explicit limits on external actions.
Weigh upPortable profile; manually load or adapt to a native agent format. No automatic subagent registration or permission grants.
Evidence review · Undominated.ai
Undominated · Resource release verifier
Independently verify packaged resources, clean installation and meaningful public availability after a release.
Why we selected itDefines a specialist role, required evidence, handoff contract and explicit limits on external actions.
Weigh upPortable profile; manually load or adapt to a native agent format. No automatic subagent registration or permission grants.
Data and retrieval · wshobson
Vector Database Engineer
Plans and implements semantic retrieval systems through corpus analysis, embeddings, chunking, index selection, hybrid search, reranking and monitoring.
Why we selected itWorkflow is requirement→embedding→chunk→store→index→hybrid→rerank→monitor, which is a real RAG build path.
Weigh upThe broad implementation role declares no tool allowlist; access to databases, credentials and file changes comes from the host.
Modernization and specifications · anthropics
Version Delta Analyst
Maps a same-stack version upgrade to the breaking and behavioral changes the actual codebase encounters, distinguishing available tooling from tooling that was run.
Why we selected itIt forbids folding analyzer output into the catalog unless the tool actually ran, and records coverage-lost when restore/network is missing.
Weigh upBody says read-only; frontmatter still grants Bash (no Write/Edit). upgrade-assistant and ng update are described as in-place editors—obedience is the only brake.
03 / BEHIND THE SELECTION
The review is part of the product.
A useful recommendation tells you why it fits—and what still needs checking.
What we inspect
We read the complete selected definition, identify its role, workflow, output expectations and verification instructions, and check the applicable licence. Review notes distinguish instructions from enforcement: a prompt saying “read only” does not itself restrict the host’s tools.
What a selection means
Each resource has a concrete use case, original selection reasons, named limitations and a dated review record. We favour specific instructions, useful scope and inspectable setup. The list is curated; it is not a census of everything available or an independently benchmarked league table.
Before using it
Read the complete review, check the upstream revision and match the resource to your own host and permissions. Review notes apply to the material named at the recorded date. Installation commands may retrieve a newer upstream version.
Where we looked
- anthropics/claude-plugins-official ↗
- github/awesome-copilot ↗
- VoltAgent/awesome-claude-code-subagents ↗
- wshobson/agents ↗
- msitarzewski/agency-agents ↗
- affaan-m/everything-claude-code ↗
- AWS Labs AI-DLC Workflows ↗
Reviewed authored personas and the documented framework projection; retained the advisory compliance role.
- Trail of Bits Skills ↗
Reviewed full worker definitions, output contracts, plugin dependencies and the CC-BY-SA licence.
- Sentry Skills ↗
Screened agent originals; recorded frontmatter exclusions and selected the original Anthropic simplifier instead of a duplicate vendored copy.
- Microsoft Skills ↗
Reviewed infrastructure and wiki agent definitions; excluded project-specific or overlapping roles.
- VoltAgent/awesome-claude-code-subagents — expanded definition review ↗
Reviewed complete candidate definitions, licensing and required host/dependency boundaries; selections are source reviews, not runtime benchmarks.
- affaan-m/everything-claude-code — expanded definition review ↗
Reviewed complete candidate definitions, licensing and required host/dependency boundaries; selections are source reviews, not runtime benchmarks.
- anthropics/claude-plugins-official — expanded definition review ↗
Reviewed complete candidate definitions, licensing and required host/dependency boundaries; selections are source reviews, not runtime benchmarks.
- github/awesome-copilot — expanded definition review ↗
Reviewed complete candidate definitions, licensing and required host/dependency boundaries; selections are source reviews, not runtime benchmarks.
- msitarzewski/agency-agents — expanded definition review ↗
Reviewed complete candidate definitions, licensing and required host/dependency boundaries; selections are source reviews, not runtime benchmarks.
- wshobson/agents — expanded definition review ↗
Reviewed complete candidate definitions, licensing and required host/dependency boundaries; selections are source reviews, not runtime benchmarks.
- Svelte primary source ↗
Direct source screening; popularity was not treated as evidence of quality.
Selections we withheld (59)
These are documented decisions from this review, not a blacklist of the wider ecosystem.
- anthropic-silent-failure-hunter: The full upstream file fails YAML parsing: the unquoted description contains embedded example text with colon-space syntax. Excluded from screened native-agent downloads; additional project-specific logging assumptions would also need adaptation.Source ↗
- anthropic-plugin-validator: The definition ends with unrelated generation-session chatter, refers to sibling validation utilities not included in a standalone download, and encodes host schema assumptions that need current validation. Kept as reviewed evidence, excluded from selected downloads.Source ↗
- github-api-architect: The role depends on a Code Interpreter environment that is not declared in its host tool configuration, and tightly couples its generation workflow to a particular service/manager architecture. Excluded in favor of more portable, source-aware architecture definitions.Source ↗
- github-scientific-paper-research: Primarily a wrapper around a specific remote BGPT MCP service, whose access terms, host configuration and evidence-quality output were not verified here. Too little standalone research methodology for the selected definition downloads.Source ↗
- github-search-ai-optimization-expert: The broad SEO/GEO checklist mixes implementation and optimization claims without a concrete evidence or audit-output contract. Named commercial analysis tools are not bundled or configured; stronger bounded research and technical roles were selected.Source ↗
- voltagent-docs-drift-editor: The otherwise narrow editing workflow incorrectly says an HTML comment preserves an old fragment anchor. It also permits a TODO mutation while describing the page as skipped. Do not promote the unchanged definition until these instructions are corrected.Source ↗
- voltagent-dependency-manager: Broad checklist persona includes fixed, apparently completed vulnerability, package and performance results as a delivery notification, without a sufficiently specific evidence/output contract. A narrower verified workflow is preferable.Source ↗
- voltagent-incident-responder: Includes operationally destructive containment actions and an unrestricted Bash/write tool set without an explicit action-authority gate; fixed successful incident metrics also appear in the delivery template. Not selected as a ready reusable response role.Source ↗
- voltagent-data-engineer: Generic broad implementation checklist asserts zero-data-loss guarantees and supplies fixed successful delivery metrics. Insufficient grounding and role-specific output constraints for this curated selection.Source ↗
- voltagent-assumption-mapping: The full upstream role has invalid YAML frontmatter: its unquoted description contains a colon followed by a space. Excluded from screened downloads rather than requiring users to repair a known-broken native definition.Source ↗
- voltagent-ab-test-analysis: The full upstream file fails YAML parsing because its description contains unquoted colon-space syntax. Its fixed-threshold decision framework also conflates minimum detectable effect with a shipping threshold and lacks a specified sequential design for extending tests.Source ↗
- voltagent-scientific-literature-researcher: Relies on a BGPT service and an unspecified context-manager integration, includes example completed research metrics, and repeats vendor evidence-quality claims without independent validation. The selected Research Synthesist provides a clearer source-assessment method without that dependency.Source ↗
- agency-design-ux-researcher: Includes fixed adoption and satisfaction targets while deferring important methodological detail to the model’s training. Research recruitment, consent, analysis and output verification are insufficiently specified for this screened collection.Source ↗
- agency-design-brand-guardian: Broad brand and trademark strategy persona with unmeasured consistency/equity targets and methodology deferred to core training. Insufficiently bounded deliverables and validation for the selected collection.Source ↗
- agency-product-sprint-prioritizer: Supplies fixed velocity, timeline and feature-success targets without an evidence workflow or configured planning integration. Excluded rather than present the persona’s targets as demonstrated planning performance.Source ↗
- agency-testing-reality-checker: Predetermines a negative assessment and grade range, treats any zero-issue report as an automatic failure, and assumes a particular local capture script and app layout. That is not a neutral evidence gate.Source ↗
- agency-project-management-experiment-tracker: Treats reaching statistical significance for nearly every experiment as a success target and supplies an illustrative revenue claim without a measurement procedure. Excluded because that framing can bias experimental interpretation.Source ↗
- wshobson-observability-engineer: An extensive prospective capability list spanning telemetry, cloud cost, compliance and chaos engineering, with little bounded output or operational authority protocol. Excluded in favor of more focused definitions.Source ↗
- wshobson-context-manager: Broad context-engineering capability lists do not provide a sufficiently concrete handoff schema or standalone memory implementation. Excluded to favor narrowly actionable roles and avoid implying that a prompt installs persistent memory.Source ↗
- ecc-build-error-resolver: Its quick-recovery section deletes the dependency lockfile and reinstalls packages, conflicting with a minimal, reproducible repair role. Excluded from the unchanged downloadable selection.Source ↗
- ecc-e2e-runner: Contains misleading Playwright guidance that raw page.click lacks auto-waiting, recommends networkidle for animation timing, and offers test quarantine plus artifact upload without enough workflow boundaries. A corrected definition would be preferable.Source ↗
- ecc-doc-updater: Assumes companion code-map generation scripts and tooling that are not included in the standalone file. It overlaps the selected documentation roles, whose repository inspection and output contracts are more reusable.Source ↗
- voltagent-content-quality-editor: Delegates its central editing step to a globally installed external unslop package that was not independently reviewed, while using fixed readability targets as a quality gate. The standalone definition is not a self-contained substantive editing method.Source ↗
- voltagent-ai-writing-auditor: The role treats unsupported stylometric frequency thresholds and blanket punctuation/hedging rules as an audit method, then rewrites the entire text. It also incorporates named external writing systems whose applicable upstream permissions were not independently verified in this pass.Source ↗
- github-refine-issue: A short generic issue-refinement checklist requests delete_issue alongside update tools without explaining or gating that unrelated destructive capability. It lacks a concrete change-review contract and was not selected.Source ↗
- github-agent-governance-reviewer: The broad governance role prescribes a Python-style policy decorator and speculative trust scoring across multiple frameworks without a concrete output contract, verification protocol or referenced implementation. It overlaps better-bounded security and threat-modeling roles and was excluded rather than presented as an implemented enforcement layer.Source ↗
- github-task-researcher: Requires deleting non-selected alternatives from the final research record and assumes a large host-specific tool collection. It substantially overlaps the selected technical-spike researcher while preserving less of the decision trail.Source ↗
- sentry-senpai: The full original fails strict YAML parsing: an unquoted description contains colon-space syntax at Examples:. Excluded from unchanged native-agent downloads.Source ↗
- sentry-code-simplifier: This vendored copy puts an attribution comment before its YAML block and duplicates the Anthropic role. Selected the valid original Anthropic definition with its applicable licence instead.Source ↗
- awslabs-aidlc-aws-platform: The persona covers live provisioning, drift remediation and teardown through inherited shell tools. The single file supplies neither an action-specific approval contract nor a fixed output schema; framework controls would need separate operational verification. Not selected for this reusable-definition expansion.Source ↗
- awslabs-aidlc-operations: Includes production chaos experiments and restart, failover and scaling runbooks without defining action-specific authorization, abort conditions or a bounded response artifact in the persona. Prefer a separately reviewed operational workflow over promoting the unchanged role as a general-purpose download.Source ↗
- trailofbits-dimension-validator: The definition assigns severity from mismatch type and broadly excludes commented conversions, test/mock code and documented edge cases from findings without requiring the same path-level verification. It also depends on prior unit annotations and host-specific task tools. The narrower evidence-driven workers were selected instead.Source ↗
- microsoft-coreai-infrastructure: This is a CoreAI DIY project runbook with fixed repository paths, Bicep modules and Azure deployment/teardown commands. It is not a portable infrastructure definition, and the unchanged file cannot supply another project’s deployment boundaries.Source ↗
- microsoft-wiki-researcher: Substantially overlaps the selected code exploration and research roles. It depends on a resolved repository/citation context and has no tools allowlist; the expansion favors more bounded workers with explicit analysis outputs.Source ↗
- AWS Incident Triage: Withheld after inspecting its required aws-cloudwatch-investigation companion: the throttling example treats every API Gateway 4XXError as a throttling event, and the previous-week comparison duplicates the same metric inside one request without shifting its time window. Current AWS API documentation does not support these interpretations. The investigation outline is useful, but the unchanged dependency can produce misleading incident evidence.Source ↗
- aws-principal-architect: Broad AWS expertise inventory lacks a concrete required deliverable or verification contract. The selected serverless architect gives a more specific design output and fills the AWS architecture gap without another overlapping generalist.Source ↗
- aws-serverless-architect: Withheld in favour of more specific, verifiable definitions. Its advice mixes an HTTP API preference with REST-only API Gateway features without explaining the boundary, asks for rough monthly costs without a pricing-source or calculator requirement, and requests working infrastructure examples without a verification gate.Source ↗
- react19-test-guardian: Contains a false React 19 Strict Mode claim and tells the agent to change spy assertions to observed call counts. Current React documentation still describes extra development effect cycles. Its passWithNoTests/forceExit-driven completion loop can also obscure missing coverage or unresolved handles.Source ↗
- arm-migration-agent: Directs automatic architecture and dependency changes while treating builds and integration validation as optional. It also requires learning_path_server, which is absent from the declared MCP tools. The unchanged workflow lacks a sufficiently reliable validation contract for architecture-specific changes.Source ↗
- Oracle-to-PostgreSQL Migration Expert: Withheld after inspecting required companion skills: migrating-oracle-to-postgres-data-access-code instructs retaining CommandType.StoredProcedure for function calls, contrary to the default behaviour documented for Npgsql 7 and later. Its risk-review skill also needs a separate references tree. The phase structure is useful, but the unchanged workflow includes a material migration error.Source ↗
- OpenAPI to Application Generator: Withheld because the procedure asks for a complete deployable application but does not define concrete OpenAPI validation, unresolved-reference handling, architecture decisions or executed acceptance checks; it largely repeats the existing scaffolding role.Source ↗
- backend-development-performance-engineer: Assigns generic latency severity thresholds and asks for expected improvement estimates without a concrete measurement protocol. The selected database and browser performance roles make stronger distinctions between observed measurements and recommendations.Source ↗
- backend-development-test-automator: Substantially overlaps the selected Test Engineer and the expanded QA and Playwright roles. Its general capability list and test-file organization add less distinctive method than the bounded alternatives.Source ↗
- backend-development-graphql-architect: Mostly a broad catalogue of GraphQL capabilities and technologies, with no specific output schema, evidence contract or failure handling. Not selected solely to fill an API-design label.Source ↗
- monorepo-architect: A compact setup checklist with no concrete validation, migration boundaries or deliverable contract. The architecture and build-related roles already cover its general planning advice.Source ↗
- eval-orchestrator: Combines static checks and model-supplied rubric/F1 scores into badges such as production ready without a defensible runtime validation contract. The workflow depends on a CLI and judge absent from the standalone definition and overstates what the composite can establish.Source ↗
- framework-migration-legacy-modernizer: A short general migration checklist substantially overlaps the existing modernization roles. The selected Uplift Migrator adds a more concrete pilot-playbook gate, unit ownership and executed-build reporting contract.Source ↗
- api-designer: The delivery template contains fixed successful endpoint and SDK counts, while the role assumes an unspecified context-manager protocol. The extensive topic lists do not establish an evidence-backed validation or completion contract.Source ↗
- a11y-architect: Misidentifies WCAG 2.2 criterion 2.4.11 as focus contrast and blends target-size/spacing advice into purported universal requirements. Current W3C documentation defines 2.4.11 as Focus Not Obscured (Minimum). The unchanged reference should be corrected before recommendation.Source ↗
- Software Architect: The bounded-context and architecture-pattern guidance is useful, but overlaps the selected Code Architect, Architecture Critic and ADR roles. This expansion prioritizes missing methods rather than another general system-design persona.Source ↗
- Test Automation Engineer: The CI example relies on an unconfigured PLAYWRIGHT_TRACE environment variable for tracing and its worker fixture is not safe across concurrent shard jobs sharing a backend. The role also prescribes fixed reliability targets and automatic test quarantine. Prefer the narrower exploration-first test role.Source ↗
- Spatial Data Scientist: Overstates that non-spatial models on spatial data necessarily produce invalid inference, and lists many spatial methods without a precise data/validation contract. The selected statistician provides clearer design and assumption boundaries without that blanket claim.Source ↗
- Language Translator: A Spanish-English travel and conversation persona rather than a software-localization workflow. Broad cultural and emergency guidance and phonetic approximations would need specialist verification; this pass does not promote it as a general translation or localisation solution.Source ↗
- Lingo.dev Internationalization: Delegates the entire procedure to a remote i18n_checklist tool whose current workflow and service requirements were not independently reviewed. The file supplies no substantive standalone localization method beyond obeying that service.Source ↗
- GitHub Community Elasticsearch Observability Agent: Withheld at this revision: the embedded MCP configuration combines a remote type with local command/args and no remote URL field. It needs a host-specific configuration correction before the advertised Elastic tools can be treated as an installable integration.Source ↗
- Agency Experiment Tracker: Withheld for experiment analysis: its success criteria reward most experiments reaching statistical significance. That is not a sound generic measure of experiment quality and can bias interpretation away from valid null results.Source ↗
- SAST and SCA analyzer: The pinned profile assigns an overall compliance PASS when no Critical or High findings are found. A bounded SAST/SCA scan cannot establish compliance with the named frameworks, and the self-assessed quality score supplies no independent validation.Source ↗
- ARM Cortex expert: The pinned profile both recommends static mut DMA buffers and later calls all static mut undefined behavior. Its critical-section example unconditionally enables interrupts after disabling them, failing to preserve a previously disabled state. Hardware-specific code needs correction and device-bound verification.Source ↗
- Healthcare reviewer: The profile emits SAFE TO DEPLOY for clinical software from an LLM code review without a validated clinical-safety acceptance contract or qualified sign-off. That verdict exceeds this source-review evidence; retain as a private candidate pending a bounded contract.Source ↗
04 / PRACTICAL ANSWERS
Before you add it.
Is an agent definition a running AI service?
No. These are reusable role and workflow instructions for an agent host. You still need a compatible tool, model access and appropriate permissions. The host and model determine what the definition can actually do.
Can I copy the complete definition?
When the applicable upstream licence permits redistribution, the detail page includes the exact reviewed definition, a download, attribution and licence text. Preserve those notices when reusing or redistributing it. Other resources link to the original instead.
Will every definition work in every AI tool?
No. Frontmatter, model aliases, tool names, installation paths and delegation behavior vary by host. Each review lists documented compatibility and relevant limitations. Adaptations need their own review; a downloaded role is not a universal installation package.
How were these roles selected?
We look for a specific job, an actionable workflow, useful output expectations and explicit checks or boundaries. Each definition has original notes explaining its inclusion. We have not benchmarked these roles against every alternative or executed them across all hosts.