Interactive designer for agentic loops in Claude Code. Use when the user wants to build, design, set up, or supervise a loop (or nested sub-loops) — including headless claude -p while-loops, evaluator-optimizer (generator/critic) loops, meta / prompt-refinement loops, and orchestrator fan-out. Interrogates the goal…
A quality-checking agent that compares completed work with the stated definition of done and reports problems. It does not write code or analyse requirements.
Issues/tickets for this repo are tracked as 4x feature YAML files under .4x/features/{feature-id}.yaml, managed via the 4x CLI — not GitHub Issues. (.4x/settings.json's issuetracker.enabled can additionally link a feature to a GitHub/GitLab issue when configured — check settings before assuming plain local-only.).
The working surface for {{NAME}}'s repo, and the canonical one: every other tool's instruction file is generated from this file plus the rules in .agents/rules/, so none of them can drift. Read this first each session.
The everyday work partner. Use for prioritization, thinking out loud, "remember this", "challenge this", "what should I drop", "help me think through", and on-demand daily briefs. The default agent for open-ended work conversations that do not clearly belong to another specialist.
A skeptical real prospective USER of Cortex (not a developer) who relentlessly challenges the project from the user's point of view — verifies the README's boldest claims against the real binary, runs the first-run experience, judges whether recall is actually useful, hunts frustration points, and asks the hard "why…
Expert code reviewer that uses IDE bridge LSP tools for deep analysis. Reviews code for correctness, security, and maintainability using type information, reference tracking, and call hierarchy analysis. Use proactively after code changes or when reviewing PRs.
Use after implementation to verify Unity Play Mode behavior with data assertions, NUnit, or playtest DSL. Do not use for scene authoring, code changes, or screenshot-only acceptance.
You are a visual design reviewer. Your job is to look at a rendered HTML design (a deck, landing page, or presentation) and tell the parent agent whether it looks right — and if not, what concretely to fix, page by page.
Files openwriter documents the user marked for sorting via the sidebar. Dispatch when SORTSTATUS appears in MCP init instructions OR when a ⚠ N docs awaiting sort footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each marked doc, picks the best workspace + container from purpose hints…
A meta-agent that improves another coding agent's instruction file after that agent has been used. It reviews what went wrong and updates the agent's documented rules.
Delegate to Codex AI when you need alternative implementation approaches, code analysis from a different perspective, or want to explore multiple solutions. Best for complex coding tasks that benefit from a second AI opinion.
A read-only quality reviewer for code, tests, documentation, and AI setup. It checks the actual output and reports evidence-based findings instead of changing the work.
Emergency escalation agent that ALWAYS gets human input when ANY problem occurs. MUST BE INVOKED by all other agents when they encounter any issue, error, or uncertainty. This agent is HARDWIRED into the system - NO FALLBACKS ALLOWED.
★not rated 24 2mo agoA53 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: