ClaudeSuperPower
SubmitLog in

scan

Skill

Runs an Aikido security scan on generated, added, or modified code files to detect SAST vulnerabilities and exposed secrets. Use when the user wants to scan code for security issues, after writing or modifying code, or when they mention Aikido, security scan, or SAST. Always run an Aikido scan after

0Security

Install

git clone https://github.com/AikidoSec/aikido-claude-plugin.git ~/.claude/skills/scan

What is scan?

Runs an Aikido security scan on generated, added, or modified code files to detect SAST vulnerabilities and exposed secrets. Use when the user wants to scan code for security issues, after writing or modifying code, or when they mention Aikido, security scan, or SAST. Always run an Aikido scan after generating code to verify the generated code is free of security issues.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~93 tokens of context used while enabled, before you invoke anything

Documentation

README · ~1 min read

When scanning the code for security vulnerabilities using the Aikido MCP server:

  1. Identify all files that were generated, added, or modified in this session (or that the user has mentioned).
  2. For each file, read its full content.
  3. Run aikido-mcp:aikido_full_scan with all files and their full content. Stay within the 50-file limit per request — batch into multiple calls if needed.
  4. If any security issues are found:
    • Explain each issue clearly: title, description, severity, file location, and line numbers.
    • Apply fixes guided by the remediation provided by Aikido.
    • After applying all fixes, run aikido-mcp:aikido_full_scan again to verify that the issues were resolved and no new issues were introduced.
    • Stopping the loop: If you can explain why the applied fix is safe (e.g. the fix correctly addresses the finding and the remaining scan output is a false positive or acceptable), you may stop and report to the user. Otherwise, repeat the fix-and-rescan cycle up to 3 attempts; if issues remain after that, report them to the user instead of continuing.
  5. Report the final scan result to the user — confirm all clear or list any unresolved issues with explanation.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills →

ECC

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

235.3K stars

claude-md-improver

Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintena

32.8K stars

Anthropic-Cybersecurity-Skills

817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io standard · Works with Claude Code, GitHub Copilot, Codex CLI, Cursor, Gemini CLI & 20+ platforms · 29 security domains · Apache 2.0

26.9K stars