Help us improve
Share bugs, ideas, or general feedback.
From aikido
Configures the Aikido plugin by setting up the API key and verifying the MCP server. Accepts an optional API key argument to configure automatically. Use when the user wants to set up or verify the Aikido plugin, after installing it, or when aikido_full_scan fails or is unavailable.
npx claudepluginhub aikidosec/aikido-claude-plugin --plugin aikidoHow this skill is triggered — by the user, by Claude, or both
Slash command
/aikido:setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When helping the user configure the Aikido security plugin:
Tests AI IDEs for MCP configuration poisoning vulnerabilities, assessing auto-loading of untrusted workspace configs and tool approval controls across four interaction tiers.
Scans Claude Code .claude/ directory for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Audits CLAUDE.md, settings.json, MCP servers, hooks, and agents.
Audits MCP server configs across project/user/plugin scopes for JSON validity, security, compliance using claude mcp CLI and file inspections.
Share bugs, ideas, or general feedback.
When helping the user configure the Aikido security plugin:
Before doing anything else, run node --version to check the installed Node.js version.
~/.claude/settings.json (create it as {} if it doesn't exist).AIKIDO_API_KEY into the env object, preserving all other existing settings. The result should look like:
{
"env": {
"AIKIDO_API_KEY": "<key>"
}
}
~/.claude/settings.json.test.js and content // test./aikido:setup <my-key>
c. Remind the user to restart Claude Code after setting the key so the MCP server picks it up.
d. Offer to verify the setup after they have set the key by running the test scan again.