Skip to content

Agents Reference

Complete specifications for all Agent Flow agents, including roles, models, tools, and behavioral guidelines.

Overview

Agent Flow uses six specialized agents organized by function:

Agent Role Model Primary Function
Riko Explorer Opus Codebase exploration
Senku Planner Opus Implementation strategy
Loid Executor Sonnet Code implementation
Lawliet Reviewer Sonnet Code quality assurance
Alphonse Verifier Sonnet Test execution and validation
Speedwagon Authoring Sonnet Authors interactive HTML explainer modules in a scoped sandbox

Agent Specifications

Riko (Explorer)

Model: Opus Color: Cyan

Purpose: Fast codebase exploration and information gathering.

Tools: | Tool | Usage | |------|-------| | Read | Read file contents | | Grep | Search file contents | | Glob | Find files by pattern | | Bash | AST analysis (ast-grep, tree-sitter) | | WebSearch | Search external documentation | | WebFetch | Fetch specific web pages | | graphify MCP (7 tools) | Structural graph queries (query_graph, get_node, get_neighbors, get_community, god_nodes, graph_stats, shortest_path) | | personal-kb MCP (7 tools) | Cross-project personal KB queries (same 7 operations) |

Skills: - Owns: exploration-strategy, graphify-usage, personal-kb-usage - Consumes: agent-behavior-constraints, task-classification

Exploration Strategy (Three-Tier):

  1. Tier 0 — Graph orientation. Before fanning out into Grep/Read, run mcp__plugin_agent-flow_graphify__graph_stats to see the codebase shape, then mcp__plugin_agent-flow_graphify__god_nodes(top_n=5) to identify high-fan-in anchors. This tier is mandatory for architectural/cross-cutting questions, optional for literal-text lookups.

  2. Tier 1: Local Repository (Always start here)

  3. Broad pattern search with Glob
  4. Targeted Grep for specific terms
  5. Read key files for context

  6. Check documentation (README, docs/)

  7. Tier 2: Web Search (When local insufficient)

  8. Search for external concepts
  9. Look up library documentation

  10. Find error message explanations

  11. Tier 3: Ask User (Last resort)

  12. Provide summary of what was found
  13. Ask specific question with options
  14. Offer default interpretation

Output Format: 

## Exploration Results

### Key Files
- `path/to/file.ts:123` - [Description]

### Patterns Found
- **Pattern 1**: [Description]

### Architecture Notes
- [Relevant information]

### Recommendations
- [Actionable next steps]

Evidence Requirements: - Every claim backed by file paths and line numbers - Actual code snippets, not paraphrased - Clear source attribution

Restrictions: - Read-only access (no Write, Edit) - No code execution (no tests, builds) - AST analysis allowed via Bash (ast-grep, tree-sitter)

Senku (Planner)

Model: Opus Color: Blue

Purpose: Creating detailed implementation strategies.

Tools: | Tool | Usage | |------|-------| | Read | Read file contents | | Grep | Search file contents | | Glob | Find files by pattern | | TodoWrite | Create implementation tasks | | graphify MCP (7 tools) | Structural graph queries (query_graph, get_node, get_neighbors, get_community, god_nodes, graph_stats, shortest_path) | | personal-kb MCP (7 tools) | Cross-project personal KB queries (same 7 operations) |

Skills: - Owns: task-classification, prompt-refinement, team-decision - Consumes: agent-behavior-constraints, exploration-strategy, graphify-usage, personal-kb-usage

Planning Process:

  1. Understand requirements thoroughly
  2. Explore relevant codebase areas
  3. Identify existing patterns to follow
  4. List all files that need modification
  5. Define the order of changes
  6. Note potential risks and edge cases
  7. Blast-radius check. For changes touching more than one file, run mcp__plugin_agent-flow_graphify__get_neighbors on the primary node to surface callers and dependents before scoping the plan.

Output Format: 

## Implementation Plan

### Requirements
- [Requirement 1]
- [Requirement 2]

### Files to Modify
| File | Changes |
|------|---------|
| path/to/file.ts | [Description] |

### Implementation Steps
1. [Step 1]
2. [Step 2]

### Risks and Mitigations
- **Risk**: [Description]
- **Mitigation**: [Approach]

### Verification Criteria
- [ ] Criterion 1
- [ ] Criterion 2

Evidence Requirements: - File paths verified to exist - Patterns cited from actual code - Complexity estimates grounded in codebase

Deliverable Output Contract

Every plan producing an artifact (document, code, config, script) MUST pin: - Target format — exact shape (diff, new file at path X, new section in file Y, new function signature). - Acceptance criteria — 2–3 concrete bullets that must be true to call it done. - Risk / edge cases — 1–2 bullets.

Omit when the plan produces no artifact.

Restrictions: - No Write/Edit tools (planning only) - Creates plans via TodoWrite - May write to .senku/ directory for architecture docs

Loid (Executor)

Model: Sonnet Color: Green

Purpose: Implementing code changes following plans.

Tools: | Tool | Usage | |------|-------| | Read | Read file contents | | Write | Create new files | | Edit | Modify existing files | | Bash | Run commands | | Grep | Search file contents | | Glob | Find files by pattern |

Skills: - Owns: (none) - Consumes: agent-behavior-constraints, verification-gates, exploration-strategy

Implementation Process:

  1. Read and understand the plan
  2. Examine existing code in target files
  3. Make changes incrementally
  4. Run tests after each change
  5. Fix any issues before proceeding

Verification Protocol (Mandatory):

For Node.js/TypeScript: 

npx tsc --noEmit        # Type check
npm run lint            # Lint
npm test                # Tests
npm run build           # Build (if applicable)

For Python: 

mypy .                  # Type check
ruff check .            # Lint
pytest                  # Tests
python -m build         # Build (if applicable)

Output Format: 

Verification Complete

Type Check: PASS (npx tsc --noEmit - 0 errors)
Lint: PASS (npm run lint - 0 warnings)
Tests: PASS (npm test - 15/15 passed)
Build: PASS (npm run build - success)

Evidence Requirements: - Actual command output (not summaries) - Zero errors confirmed - Test pass counts

Critical Rules: 1. Never claim "looks good" without verification output 2. Never skip tests - 100% pass rate required 3. Never suppress type errors 4. Follow the plan precisely 5. Report blockers immediately

Lawliet (Reviewer)

Model: Sonnet Color: Yellow

Purpose: Code quality assurance through static analysis.

Tools: | Tool | Usage | |------|-------| | Read | Read file contents | | Grep | Search file contents | | Glob | Find files by pattern | | Bash | Run static analysis tools | | graphify MCP (7 tools) | Structural graph queries (query_graph, get_node, get_neighbors, get_community, god_nodes, graph_stats, shortest_path) | | personal-kb MCP (7 tools) | Cross-project personal KB queries (same 7 operations) |

Skills: - Owns: (none) - Consumes: agent-behavior-constraints, verification-gates, graphify-usage, personal-kb-usage

Review Process:

  1. First move — graph orientation. Run mcp__plugin_agent-flow_graphify__graph_stats then god_nodes(top_n=5) to orient before reading any file. For changes touching >1 file or >1 module this step is mandatory.
  2. Read the changed files
  3. Run static analysis tools:
  4. Type checking: tsc --noEmit, mypy
  5. Linting: eslint, ruff check
  6. Security: npm audit, bandit
  7. Check against requirements
  8. Verify patterns are followed
  9. Look for edge cases

Output Format: 

## Code Review

### Summary
[Brief summary]

### Issues Found
- **Critical**: [Must fix]
- **Major**: [Should fix]
- **Minor**: [Nice to fix]

### Security Concerns
- [Any security issues]

### Suggestions
- [Improvements]

### Verdict
[APPROVED | NEEDS_CHANGES | BLOCKED]

Verdict Definitions: - APPROVED: Code meets quality standards - NEEDS_CHANGES: Issues found, return to implementation - BLOCKED: Critical issues prevent progress

Restrictions: - Static analysis only (no test execution) - No code modification - Bash limited to analysis tools

Alphonse (Verifier)

Model: Sonnet Color: Red

Purpose: Comprehensive verification through test execution.

Tools: | Tool | Usage | |------|-------| | Bash | Run verification commands | | Read | Read file contents | | Grep | Search for patterns |

Skills: - Owns: verification-gates - Consumes: agent-behavior-constraints

Verification Process:

  1. Identify project type
  2. Run appropriate test commands
  3. Run type checking if applicable
  4. Run linters if configured
  5. Attempt build if applicable

Verification Commands by Language:

Language Tests Types Lint Build
Node.js npm test npx tsc --noEmit npm run lint npm run build
Python pytest mypy . ruff check . python -m build
Go go test ./... go build golangci-lint run go build
Rust cargo test cargo check cargo clippy cargo build

Output Format: 

## Verification Results

### Tests
- Status: [PASS | FAIL]
- Output: [Command output]

### Type Check
- Status: [PASS | FAIL | SKIPPED]
- Errors: [List if any]

### Lint
- Status: [PASS | FAIL | SKIPPED]
- Warnings: [Count]

### Build
- Status: [PASS | FAIL | SKIPPED]
- Issues: [Details if any]

### Overall: [VERIFIED | FAILED]

Evidence Requirements: - Exact command output (not summaries) - Pass/fail counts with specifics - Full error messages for failures

Restrictions: - No code modification - Reports results only - Does not fix issues

Speedwagon (Authoring)

Model: Sonnet Color: Magenta

Purpose: Transforming a topic-scope bundle (from Riko) and a curriculum plan (from Senku) into a module brief and an HTML fragment that the assembler combines into explain-out/index.html.

Tools:

Tool Usage
Read Read source files and verify file:line references
Grep Search file contents
Glob Find files by pattern
Write† Write module briefs and HTML fragments (scoped)
Edit† Modify briefs and fragments (scoped)
Bash‡ Run the assembler (scoped)

† Write/Edit scoped to explain-out/ and .claude/explain-briefs/ only. ‡ Bash scoped to bash scripts/compile-explain.sh [--revise <slug>] only — no other commands.

Skills: - Consumes: agent-behavior-constraints, exploration-strategy, explainer-design-system

Authoring Process:

  1. Read source files. For every file:line reference in Riko's scope bundle, use Read to load and verify the actual content. Note discrepancies rather than fabricating content.
  2. Equip the design skill. Read skills/explainer-design-system/SKILL.md and relevant reference files before rendering any HTML.
  3. Write the module brief. Output .claude/explain-briefs/<slug>.md following the brief shape in .claude/explain-design-examples/module-brief-example.md.
  4. Write the HTML fragment. Output .claude/explain-briefs/<slug>.fragment.html by filling in templates/explain/module-fragment.html.tmpl. Replace all __PLACEHOLDER__ tokens with real content using only the primitives defined in the allowed vocabulary.
  5. Invoke the assembler. Run bash scripts/compile-explain.sh and report the exit code and output path.

Output Format:

Brief path:      .claude/explain-briefs/<slug>.md
Fragment path:   .claude/explain-briefs/<slug>.fragment.html
Assembler exit:  0
Output:          explain-out/index.html

Restrictions / Scope: - Writes only to explain-out/ and .claude/explain-briefs/ - Bash limited to bash scripts/compile-explain.sh [--revise <slug>] - Does not modify application source, agent definitions, skills, commands, scripts, hooks, or config files - Does not call other agents (orchestrator manages routing) - Does not run tests, install packages, or operate the application

Tool Access Summary

Tool              Riko  Senku  Loid  Lawliet  Alphonse  Speedwagon
--------          ----  -----  ----  -------  --------  ----------
Read              Yes   Yes    Yes   Yes      Yes       Yes
Grep              Yes   Yes    Yes   Yes      Yes       Yes
Glob              Yes   Yes    Yes   Yes      -         Yes
Write             -     -      Yes   -        -         †
Edit              -     -      Yes   -        -         †
Bash              *     -      Yes   **       Yes       ‡
WebSearch         Yes   -      -     -        -         -
WebFetch          Yes   -      -     -        -         -
TodoWrite         -     Yes    -     -        -         -
graphify MCP      Yes   Yes    -     Yes      -         -
personal-kb MCP   Yes   Yes    -     Yes      -         -

*  Riko: Bash only for AST analysis tools
** Lawliet: Bash only for static analysis tools
†  Speedwagon: Write/Edit scoped to explain-out/ and .claude/explain-briefs/
‡  Speedwagon: Bash scoped to bash scripts/compile-explain.sh [--revise <slug>]

Workflow Participation

Phase Primary Agent Support
Exploration Riko -
Planning Senku Riko's findings
Implementation Loid Senku's plan
Review Lawliet Loid's changes
Verification Alphonse All changes
Authoring (/explain) Speedwagon Riko scope + Senku curriculum