Grok Build

Validates .grok/hooks/*.json, the project hooks Grok Build loads and silently refuses when they are malformed. What a defect costs depends on where it is: a wrong-typed field or a handler with no type refuses the whole file, an uncompilable matcher drops that group, an unknown event skips its entries, and a handler with nothing to run drops that handler — none of it reported, because grok inspect emits no configuration warning for any of them. Grok accepts several spellings of every event, including Cursor's, so a shared hooks file is not reported for the spelling it uses. grok-agent-valid covers the other surface Grok refuses in silence: a .grok/agents/*.md subagent missing the name or description its loader registers it by. Grok reads AGENTS.md for portable instructions and portable Agent Skills from .grok/skills/, and its rules, commands and agent prose get the content and security rules every format shares, so no Grok-specific instruction format is validated. Enabled automatically when a .grok/ project layer exists.

Rule ID	Description	Default Severity	Autofix
grok-agent-valid	.grok/agents/*.md must declare a name and a description in frontmatter	error (auto)	-
grok-hooks-valid	.grok/hooks/*.json must use Grok's hook events, handler types and fields	error (auto)	-