The package automatically installs its bundled agent personas into Pi discovery directories during npm install. The behavior is limited to this package’s own extension, which warrants a warning under the agent extension lifecycle risk rule; I found no broader agent configuration changes or network activity in the installer.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install, through the postinstall lifecycle script.
Impact
The installed personas become available to Pi as agent instructions and specify their tool access. This is limited to the package’s own agent extension, but happens automatically at install.
Mechanism
Copies personas into a project .pi/agents directory or symlinks them into the configured user agent directory; it can also remove stale package symlinks from ~/.agents.
Evidence
package.jsonbin/install-agents.mjsagents/implementer.mdagents/*.md<project>/.pi/agents/*.md$PI_CODING_AGENT_DIR/agents/*.md or ~/.pi/agent/agents/*.md~/.agents/*.md