agent-identifier

To craft frontmatter for Claude Code agents, you define a rigorous schema covering name, description, model, color, tools, dependencies, and safety checks. This process enforces project conventions and integrates with validation scripts to ensure metadata correctness.

Agent metadata validation is the process of checking frontmatter fields like name, model, and tools against a defined schema. It uses validation scripts to ensure CLAUDE.md alignment, correctness, and safety across the repository.

To add toxicity checks to agent metadata YAML files, you include the is_toxic and toxic_reason fields in your frontmatter specification. This records safety considerations and assesses potential toxicity for Claude Code agent definitions.

Yes, the agent frontmatter specification supports custom dependencies and components. It standardizes these metadata fields within YAML files to ensure all required project conventions are met and validated across the repository.

Your Claude Code agent validation script fails on missing frontmatter because the specification rigorously enforces required fields like name, description, and model. It checks YAML frontmatter alignment to ensure metadata correctness and safety before execution.

The best way to standardize agent metadata across a repository is to apply a precise frontmatter schema with automated validation scripts. This enforces consistent field definitions and safety checks for all Claude Code plugins.