Aikido Security
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This looks like a legitimate Aikido Security integration, but it documents broad authenticated API access that could change or delete Aikido data without clear approval limits.
Use this skill only if you trust the Membrane CLI and want an agent to access your Aikido Security account. Before allowing write, patch, delete, or raw proxy requests, review the exact endpoint and data being sent, and use a least-privileged account or connection where possible.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken or overly broad request could alter or delete Aikido Security data, such as findings, repositories, or user-related records.
This gives the agent an authenticated raw API escape hatch, including methods that can modify or delete data, rather than limiting it to safer scoped actions.
When the available actions don't cover your use case, you can send requests directly to the Aikido Security API through Membrane's proxy... `-X, --method` | HTTP method (GET, POST, PUT, PATCH, DELETE).
Prefer listed Membrane actions, use explicit user confirmation for any non-GET or proxy request, review endpoint paths and request bodies, and use least-privileged Aikido access.
Installing and using the skill can grant the agent reusable access to Aikido Security through Membrane.
The integration needs authenticated Membrane/Aikido access with automatic credential refresh. This is expected for the purpose, but it is sensitive account authority.
Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
Authenticate only with an account you intend the agent to use, prefer least-privileged permissions, and revoke the connection when it is no longer needed.
Future npm package changes could affect what commands do, even though the package is purpose-aligned.
The skill asks users to install a global npm CLI at the latest version. This is central to the integration, but @latest means the installed code can change over time.
npm install -g @membranehq/cli@latest
Install from the expected npm package source, consider pinning a known CLI version, and keep the CLI updated deliberately.