What one command wires
Wire Gemini CLI to Vulnetix. Skills install to ~/.agents/skills, which Gemini CLI reads in preference to its own directory, and the MCP server supplies live vulnerability intelligence.
vulnetix agent install --agent gemini-cli- 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 Gemini CLI reads skills
Agent Skills is an open standard, but hosts disagree about the directory. The installer writes the one Gemini CLI actually opens.
- Everywhere, for you:
~/.agents/skills - This repository:
.agents/skills
Add the MCP server
{
"mcpServers": {
"vulnetix": {
"httpUrl": "https://mcp.vulnetix.com/mcp",
"headers": { "Authorization": "ApiKey <orgId>:<key>" }
}
}
}True of Gemini CLI specifically
- Within a tier, Gemini CLI prefers ~/.agents/skills over ~/.gemini/skills, so the interoperable copy wins.
Ask something training data cannot answer
No install and no local binary: one URL and one header give the agent live vulnerability intelligence it can call mid-conversation.
>
is CVE-2021-44228 still actively exploited?
→ calling vulnetix_vuln
org.apache.logging.log4j:log4j-core@2.14.1 · maven
17 vulnerabilities · 11 critical, 4 high
- CVE-2021-44228 critical · CVSS 10.0 · EPSS 100.0%
- CVE-2021-45046 critical · CVSS 9.2 · EPSS 100.0%
- CVE-2021-44832 critical · CVSS 9.3 · EPSS 97.9%
CISA KEV · due 2021-12-24 · known ransomware use