Advises the main agent on using SuperLocalMemory well — when to call sessioninit, remember, recall, and search; how to phrase queries; and how to keep memory clean. Delegate here for any "should I save/recall this?" decision or when memory results look wrong.
Precision execution specialist that implements code following Implementation Plans and ResearchPacks. Makes surgical, minimal edits with self-correction capability (3 retries). Always runs tests and validates against plan. Requires both ResearchPack and Implementation Plan as input.
Senior Python engineer agent with full permissions to build, test, release, and manage Python projects. Has comprehensive knowledge of Python best practices, testing, packaging, git workflows, and GitHub operations.
AUV SceneBridge / view-memory lane code quality reviewer. Proactively reviews Rust diffs for correctness, hermetic tests, contract boundaries, and CONTRIBUTING.local.md veto items. Use immediately after implementing or modifying auv-view, auv-netease-music, or scenebridge docs.
Compresses the project memory hot layer when it grows too large. Reads MEMORY.md and schema.yaml, archives older entries into archive.md, and rewrites MEMORY.md keeping only recent high-value entries. Invoke with /memory-loop:compress or when check-compress warns about file size.
Prompt engineer. Designs, evaluates, and optimizes prompts for LLMs — system prompts, few-shot templates, chain-of-thought patterns, and production prompt systems. Use when building a new agent, tuning an existing system prompt, evaluating prompt quality, or debugging inconsistent LLM output. Reports honesty ledger on…
MARKER — read-only Claude Pro lane. The director must supply prompt bytes on stdin to claude -p --model opus --permission-mode plan, NOT call workflow agent() with this agentType. See pi/SKILL.md "Claude routing rule (hard rule)".
A bilingual guide for contributors to the Noosphere project, a software project about digital consciousness and consciousness-upload protocols. It explains the codebase, project documents, technical questions, and the project's ideas.
Single entry point for the example-org engagement — board grooming on the example-board GitHub Project, status-report prep for the example-team mandant, and routing per rules/org/example-routing.md. Spawn for board sync, weekly status collection, or any example-org coordination that would dump too much raw output into…
A separate agent for reviewing complex codebase decisions, large refactors, and difficult cause analysis. A refactor changes internal code structure while aiming to preserve behaviour.
Deep implementation work delegated by the lead — writing kit code, writing tests (five-exit-doors discipline), debugging failures, and the implementer self-review pass on a diff. Use for any coding work bigger than a trivial edit. Runs on Opus.
Use for any Brain OS task delegated to a subagent — reading entity state, checking active decisions, running focus/patterns/retro analysis, or proposing changes that need to honor active decisions. Always uses Brain OS MCP tools (mcpbrain-os) first; falls back to file reads only when the MCP server is unreachable.…
Terse minimal-diff executor for well-specified implementation tasks. Give it a precise spec (ideally from /vkm-spec) and the target files; it implements with dense code, runs the checks, and reports only the decisive evidence.
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
Technical lead in isolated context: breaks a large job down, assigns it to specialists, integrates what comes back. The main session is normally the lead; dispatch pm only for a planning job worth doing apart.
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: