ash-guide

name: ash-guide description: | Use when summoning Rune agents, when encountering "agent not found" errors, when selecting which review agents to use, or when checking agent capabilities and tools. Quick reference for all 116 agents across 8 categories (74 core in agents/ — investigation, meta-qa, qa, research, review, utility, work + 42 extended in registry/ — investigation, review, testing, utility, work). Plus 13 shared resources in agents/shared/. Keywords: agent list, Ash, subagent type, agent not found. user-invocable: false disable-model-invocation: false allowed-tools: - Read - Glob

Ash Guide

Quick reference for all Rune plugin agents, their roles, and invocation patterns.

Invocation Models

Direct Invocation (standalone tasks, custom workflows)

All Rune agents are plugin agents. Invoke with the rune: namespace prefix:

Agent rune:review:ward-sentinel("Review these files for security")
Agent rune:review:ember-oracle("Check performance bottlenecks")
Agent rune:utility:runebinder("Aggregate review findings")

Common mistake: Using agent name without namespace prefix.

# WRONG - agent not found
Agent ward-sentinel(...)

# CORRECT - full namespace
Agent rune:review:ward-sentinel(...)

Composite Ash Invocation (review/audit workflows)

The /rune:appraise and /rune:audit commands use general-purpose subagents with composite Ash prompt templates from agents/. Each Ash embeds multiple agent perspectives into a single teammate. This is intentional — composite Ashes don't map 1:1 to individual agent files.

Agent({ subagent_type: "general-purpose", team_name: teamName, name: "ash-name", prompt: /* from ../../agents/{category}/{role}.md */ })

The agent file allowed-tools are not enforced at runtime for composite Ashes. Tool restriction is enforced via prompt instructions (defense-in-depth).

Note: Agents listed below with rune:review:*, rune:testing:*, or rune:utility:* types may live in registry/ rather than agents/. Registry agents cannot be spawned directly via Agent({ subagent_type: "rune:review:blight-seer" }) — the plugin-namespaced type won't resolve. Instead, use subagent_type: "general-purpose" and inject the agent body via the agent_detail(name) MCP call or Read("registry/{category}/{name}.md"). Agents in agents/ (e.g., ward-sentinel, ember-oracle, flaw-hunter) ARE directly spawnable via their listed type names.

Review Agents

Review-style agents (in agents/review/; an additional set lives in registry/review/ and is loaded on-demand):

v3.0.0-alpha.1+alpha.2 removed: design-system-compliance-reviewer, ux-heuristic-reviewer, ux-interaction-auditor, design-implementation-reviewer were retired with their consumers. UX/design review now uses the surviving ux-flow-validator, ux-cognitive-walker, and aesthetic-quality-reviewer.

Ash Roles (Consolidated Teammates)

In /rune:appraise, agents are grouped into 7 built-in Ashes (extensible via talisman.yml):

Note: Forge Warden, Ward Sentinel, Veil Piercer, and Pattern Weaver embed dedicated review agent files. Glyph Scribe and Knowledge Keeper use inline perspective definitions in their Ash prompts (no dedicated agent files).

Utility Agents

Research Agents

Work Agents

Testing Agents (Registry — Not Directly Spawnable)

These agents live in registry/testing/ and are spawned indirectly by the /rune:testing skill during arc Phase 7.7. They cannot be passed to the Agent() tool's subagent_type parameter directly.

Ash Selection Logic

The /rune:appraise command selects Ash based on file extensions (Rune Gaze):

Ward Sentinel, Pattern Weaver, and Veil Piercer are selected for every review regardless of file types.

See roundtable-circle skill for full Ash architecture and prompts.