What one command wires
Wire Pi to Vulnetix. Pi reads ~/.agents/skills and .agents/skills, so the same skills serve it and every other agent that follows the Agent Skills standard.
vulnetix agent install --agent pi- Agent Skills: supported —
~/.agents/skills - Dependency guard: not wired by the installer —
hook contract not yet verified - MCP server: supported —
https://mcp.vulnetix.com/mcp
Where Pi reads skills
Agent Skills is an open standard, but hosts disagree about the directory. The installer writes the one Pi actually opens.
- Everywhere, for you:
~/.agents/skills - This repository:
.agents/skills
Point Pi at the MCP server
{
"mcpServers": {
"vulnetix": {
"type": "http",
"url": "https://mcp.vulnetix.com/mcp",
"headers": { "Authorization": "ApiKey <orgId>:<key>" }
}
}
}True of Pi specifically
- Pi also reads ~/.pi/agent/skills; the installer writes the interoperable path so one copy serves several agents.
The ordinary case: nothing is wrong
Across 33 everyday commands the guard produced no output at all. Silence when the policy is satisfied is what makes a guard liveable; one that comments on every install gets switched off.
$
npm install
(no output — a lockfile install adds nothing new)
$
npm i left-pad
(no output — clean package, nothing to say)
$
git commit -m "add http client"
(no output)
19 ms per tool call. 0 of 33 everyday commands
produced a single line.