311 tagged agentic-workflows, measured the same way as everything else here.
Browse within: agent-orchestration 83Autonomous Agents 53agent-harness 42bun 42claude-code-agents 27automated-testing 26agentic-coding 25agentic-appsec 23appsec 23container-scanning 23endor-labs 23malware-response 23governance 19autonomous-agent 17
Agent Claude Code
System design orchestrator. Turns a system/problem into a rigorous System Design Doc, then runs an adversarial design review. Use via Task tool for delegation, or /system-design:run for direct invocation.
Agent
Audits .context/ project content (references, docs, plans, issues, roadmap, requests, decisions, audits) for structural compliance.
Agent
Audits installed Claude Code plugins for always-loaded subagent cost vs. recent usage; flags uninstall candidates.
Agent
Audits skills across all scopes for structural issues, frontmatter compliance, and scope placement.
evgenii-studitskikh/Claude-Code-SaaS-Studio
Agent Claude Code
Supabase schema, RLS policies, multi-tenancy & auth wiring. Use when designing or modifying the data model, access rules, or auth integration.
evgenii-studitskikh/Claude-Code-SaaS-Studio
Agent Claude Code
Deploy, CI/CD, envs, observability, and launch. Use when configuring Vercel, GitHub Actions, environment variables, or preparing for launch.
evgenii-studitskikh/Claude-Code-SaaS-Studio
Agent Claude Code
Next.js App Router routes & React components. Use when building pages, layouts, forms, or client-side interactions.
Agent
Use this agent when code has been changed, written, or modified and needs quality assurance review. This agent should be used PROACTIVELY in the following situations: after code changes are made, before merges, during pull requests, when checking code for security vulnerabilities, performance issues, or…
Agent
Use this agent when you need to actively test applications, APIs, infrastructure, or code for exploitable vulnerabilities. This agent thinks like an attacker and finds entry points before real attackers do. It complements the security-master agent through practical attack simulation. This agent should be used…
Agent
Phase-aware orchestrator and entry point for every project. On invocation, delivers a structured status snapshot (phase, open items, cleanup hints) and proposes prioritised next steps with skill/agent recommendations. Disambiguates unclear requests and hands off with a bundled context. Used at session start, for "what…
Agent
MyACE project-specific orchestrator. Extends the global orchestrator with MyACE-specific subagents, commands, and conventions for the three-component architecture (backend FastAPI, frontend React/Vite, CLI Typer).
Agent
Curates what goes into an agent's context window across a long-running or multi-agent task — deciding what stays, what gets summarized, and what gets dropped.
Agent
Designs and iterates on prompts, system instructions, and agent/skill copy — owns defining what "better" means for a change before making it, not after.
Agent
CIEL's elite intelligence and ML guild. Specializes in Python systems, ML Ops, and AI integration.
Agent
CIEL's elite strategy and operations guild. Specializes in startup growth, research, and workflow automation.
Agent
CIEL's elite systems engineering guild. Specializes in Rust, C++, Go, Elixir, and high-performance architecture.
Agent
Dispatch as a subagent to execute a specific analysis task. Receives full task specification from the orchestrating agent. Does NOT inherit session context. Examples: Context: An orchestrating agent is running subagent-driven-analysis. user: "Execute Task 3: numeric feature preprocessing" assistant: "Dispatching…
Agent
Use after statistical review has passed to check code quality of analysis code. Reviews for vectorization, reproducibility, clarity, and artifact correctness. Examples: Context: Statistical review has passed for a feature engineering task. user: "Statistical review approved the feature engineering code" assistant…
Agent
Use after an analyst subagent completes a task to verify statistical correctness. Reviews for data leakage, correct metric selection, proper cross-validation, and sound statistical methodology. Examples: Context: A feature engineering task has been completed. user: "Feature engineering for numeric columns is done"…
Agent
Adversarial skeptic for the lens VERIFY stage — takes ONE candidate finding and tries to refute it against the real source, defaulting to refuted for unproven bug/correctness/security/test claims and kept for spec/plan judgment. Owns the verified flip. Read-only.
Agent
Generates all Claude Code tooling artifacts (CLAUDE.md, rules, skills, agents, hooks, MCP, output styles, snapshots, telemetry) from a codebase analysis report and wizard answers. Dispatched by /onboard:start Phase 6 and onboard:generate; hard-fails if invoked without dispatchedAsAgent=true.
Agent
Independently verifies features in a running application against the verification steps in docs/feature-list.json. Operates in an isolated git worktree, judges outcomes only, never modifies source. Spawned by /onboard:verify.