configured-agent

To make Claude Code plugin behavior configurable per project, you store plugin-specific settings in local markdown files with YAML frontmatter. The configured agent reads these local configuration files to apply project-specific overrides.

YAML frontmatter parsing works by reading boolean, numeric, string, and list values from user-managed local markdown files. The agent checks file presence and honors enabled flags and other configuration values to drive behavior.

Yes, you can use hook automation to adjust actions based on project-level settings. Hooks, commands, and agents integrate with local configuration files to adapt their actions according to the parsed YAML frontmatter.

You enable strict validation for one repository by editing only the local settings file in that project. The configured agent reads the YAML frontmatter in the matching .local.md file and applies the project-specific overrides.

Yes, this approach supports agent state persistence by storing plugin-specific settings and state in .claude plugin-local markdown files. The agent reads and applies these per-project configuration values during execution.

The limitation of managing plugin settings through local markdown files is that configuration requires manual editing of YAML frontmatter. The agent must parse frontmatter fields and check file presence, adding overhead to settings management.