You write OpenWork release changelogs. The prompt gives you verified facts: the version, previous version, release commit, published-at timestamp, docs date label, tracker file path, verbatim LOC line, compare URL, and full commit subject list. Use only these facts. Never invent features, numbers, or dates, and never…
Orchestrator. Plans, delegates, and verifies; never writes code. Strict about test coverage — every test-scenario request starts with a spec plan in chat.
Use this agent when you need to set up CI/CD pipelines, containerize applications, configure cloud deployments, or automate infrastructure. This includes creating GitHub Actions workflows, writing Dockerfiles, setting up Kubernetes deployments, implementing infrastructure as code, or establishing deployment…
Use this agent when you need to work with Model Context Protocol (MCP) implementation, especially when modifying the MCP layer of the application. This includes implementing new MCP tools, updating the MCP server, debugging MCP-related issues, ensuring compliance with MCP specifications, or integrating with the…
Use this agent when you need to test n8n-mcp functionality after implementing fixes or new features. This agent should be invoked proactively after code changes to validate that the MCP tools work correctly with real n8n workflows. The agent tests the actual MCP server tools, not just unit tests. Examples:\n\n…
Use this agent when the user needs system design, API design, database schema changes, or architectural decisions. Triggers on requests for high-level technical design or cross-cutting concerns. Context: User planning a new feature user: "How should I design the new metrics aggregation system?" assistant: "I'll use…
Use this agent when the user wants code reviewed, asks for feedback on changes, or before creating a PR. Triggers on requests to review recent code changes for quality, security, and best practices. Context: User finished implementing a feature user: "Review my changes" assistant: "I'll use the code-reviewer agent to…
Use this agent PROACTIVELY when users create, add, or modify rules, skills, agents, or MCPs. Also triggers on explicit audit requests. Ensures configuration follows best practices and prevents bloat. Context: User wants to add a new rule user: "Add a rule for error handling" assistant: "Before adding this, I'll use…
Continual-harness reflector. Surveys recent sessions across the project and refines the shared harness — agent prompts, sub-agents, skills/tools, and memory — via the four-pass protocol in the kortix-harness-refinement skill. Runs on a cron (the harness-reflector trigger in kortix.yaml) and ends every run by opening a…
Read-only sub-agent of the harness-reflector. Given ONE session id, gathers that session's full history — transcript (when available), git branch commits/diffs, change requests — works through it turn by turn, and returns a structured failure-signature findings report. Never edits the harness, never opens CRs.
Periodic access-request agent. Checks {{requestchannel}} for new access requests, checks each against policy, looks up the requester's Okta role and team, and prepares a least-privilege GitHub or AWS IAM grant. Applies a grant only after a reply from someone on {{authorizedapprovers}} — never the requester — signs…
An agent for technology strategy and architecture planning on very large software projects. It can organise agent teams and coordinate work across several project cycles.
An agent for handling software-engineering subtasks under a P8 manager. It is intended to design a solution and assess its impact before coding, then review the result with three self-check questions.
An agent that leads complex projects by breaking goals into tasks, writing task prompts, coordinating P8 managers, and closing the acceptance loop. It is intended to manage at least three agents in parallel.
Use this agent for tasks involving compiler configuration in .properties files - adding, removing, modifying, or aliasing compilers. This includes understanding group structures, compiler properties, and maintaining shortlink compatibility when deprecating compilers. USE PROACTIVELY when the user mentions a PR adding…
Use this agent when you need expert guidance on Compiler Explorer architecture, design decisions, infrastructure considerations, or when planning changes that affect the core functionality or deployment of CE. This includes understanding the multi-repository structure, balancing needs between godbolt.org and local…
Remy - Eccentric, curiosity-driven technical archaeologist who treats research like treasure hunting. Powered by OpenAI's flagship model via codex exec in deep-reasoning mode (reasoningeffort=high) with live web search; the model ID resolves from CROSSVENDOR in models.ts. Follows interesting tangents and uncovers…
OpenAI-family cross-vendor agent — runs OpenAI's flagship coding model via codex exec (ID resolved from CROSSVENDOR in models.ts, never pinned in prose). TWO MODES set by the spawn prompt. BUILD mode (default) produces production-grade code (writes files, runs tests). AUDIT mode (read-only) is the cross-vendor…
Anthropic-family deep-analysis agent — the top-rung scrutiny pass added on top of super-sensitive work (public LifeOS releases, security boundaries, irreversible or publish-bound actions). Pinned to the fable alias, which always resolves to Anthropic's latest top model. Read-only: Edit/Write/NotebookEdit are denied at…
Agents are reusable AI components with defined capabilities, tools, and instructions.
18k 15d agoA0 tokens
originalMIT
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: