Agent Files

Location

Agent files are stored in .claude/agents/:

.claude/agents/
  planning-agent.md
  frontend-agent.md
  backend-agent.md

AGENT.md Structure

Each AGENT.md file has YAML frontmatter followed by markdown body:

---
name: agent-name
description: One-line description of what the agent does and when to use it
tools: Read, Glob, Grep
---

# Agent Name

You are an expert <role>. Your mission is to <goal>.

## Process
...

## Patterns
1. Pattern one — discovered convention to follow.
2. Pattern two — ...

The frontmatter fields:

• name — required. The agent's identifier (lowercase, hyphenated). Claude Code derives the agent id from this field, not the filename.
• description — required. What the agent does and when Claude should delegate to it; also surfaced in /hypr:list and /hypr:status.
• tools — optional. Restrict the agent to specific tools (e.g. Read, Glob, Grep for a read-only reviewer). Omit to inherit all tools.

The markdown body typically contains: a Role paragraph, a Process section (numbered steps), and a numbered list of Patterns (project-specific conventions discovered during assessment, referenced by number elsewhere). For real examples, see the assessment-output sample agents.

Modifying Agents

You can manually edit agent files to add custom rules or adjust patterns. Changes take effect immediately.

Optional Agents

Beyond the core agents, you can install optional agents and skills from the Hypr directory:

Optional agents extend Hypr's capabilities for specific use cases:

• accessibility-analyzer - WCAG 2.1 compliance auditing
• security-scanner - Security vulnerability detection
• testing-agent - Test suite generation
• migration-agent - Framework migration assistance