Appearance
Why It Matters
SEC357 flags plugin agent markdown whose frontmatter sets hooks.
For shared plugin agents, this is a poor place to define hook behavior:
- it mixes execution wiring into agent content
- it makes review harder because content and runtime hooks are coupled
- it conflicts with the plugin-agent boundary documented for Claude plugin agents
What Triggers
This rule applies only to plugin agent markdown surfaces and triggers on parsed frontmatter that contains the exact key:
hooks
Example that triggers:
yaml
---
hooks:
on-save: ./hooks/review.sh
---Examples that stay clean:
- plugin agents without
hooksin frontmatter - fixture-like paths under
tests/,fixtures/,examples/, orsamples/ - ordinary
SKILL.mdcontent outside plugin-agent surfaces
False Positives
This rule stays Preview because some repos may still experiment with unsupported plugin metadata. The signal is structural policy guidance, not evidence that the hook itself is malicious.
Remediation
Remove hooks from plugin agent frontmatter and keep hook execution in plugin-level hook configuration instead.