Aikido Issues

by AikidoSec02f018ad4da1No license14 starsListed Oct 7, 2026Updated Oct 7, 2026Repository updated 12 days ago

List, count, summarize, or triage security issues from the Aikido security feed. Use when the user asks about Aikido findings, vulnerabilities, leaked secrets, SAST/IaC/SCA results, cloud or container security issues, or EOL/license/malware alerts surfaced by Aikido.

Instructions onlySecurity
AI-generated overview

Lists, counts, summarizes, or triages security issues from the Aikido security feed via the Aikido MCP server.

What it does
This skill guides an agent in querying the Aikido security feed through the aikido-mcp:aikido_issues_list tool. It supports listing, counting, summarizing, and triaging findings, with optional filters for scope, issue type, and SLA status, plus pagination and single-issue detail lookup by ID. Results are presented in a fixed per-issue format showing title, ID, type, severity, and remediation, with extra fields such as file, location, link, or SLA due date when relevant. If the Aikido MCP server is unavailable, the skill instructs the agent to tell the user and point to setup steps.
When to use it
Use it when a user asks about Aikido findings, vulnerabilities, leaked secrets, SAST/IaC/SCA results, or cloud, container, EOL, license, or malware alerts surfaced by Aikido. It also fits requests to dig into, explain, triage, or fix a specific Aikido issue by ID.
Requirements
Requires the Aikido MCP server with the aikido_issues_list tool; no scripts are shipped, and the skill is instructions only.

When listing Aikido feed issues:

  1. Use aikido-mcp:aikido_issues_list
  2. Call it when the user wants to list, show, count, or summarize Aikido feed issues.
  3. Pass scope fields only when the user (or workspace context) supplies them: cloud_name, repo_name, repo_branch_name, vm_name, domain_name, container_name, team_name, workspace_name.
  4. Optional issue_types (array): open_source, leaked_secret, cloud, sast, iac, surface_monitoring, malware, eol, mobile, docker_container, cloud_instance, scm_security, license, ai_pentest — e.g. include leaked_secret for secrets. Omit when no category filter is needed.
  5. SLA filters (booleans): set out_of_sla: true when the user wants issues that are past their SLA, or sla_due_soon: true for issues approaching their SLA deadline.
  6. Pagination: use numeric page only when the user needs more than the first page of results (zero-indexed). Only 25 findings are reported per page. Report to the user if there are more findings on following pages.
  7. Detail lookup: pass issue_id (string) to fetch one issue with more detail than the list returns. Use it when the user asks to dig into, explain, triage or fix a specific issue, or names an issue by its ID. issue_id overrides every other filter — the call returns that single issue, so do not combine it with scope, type, SLA or pagination fields.
  8. Present each issue exactly in this form (increment #):
    Issue #1: <issue_title> - ID: <issue_id> - Issue type: <issue_type> - Severity: <issue_severity> (<issue_severity_label>) - Remediation: <issue_remediation>
    Add extra bullets when the field is relevant, e.g. File: <issue_file> (line <issue_start_line>), Location: <location.type> <location.name> (<location.branch_name>), Issue link: <issue_link>, SLA due date: <issue_remediate_by_date>.
  9. For an issue_id lookup, keep the same format and then summarize the extra fields the detailed response carries.

If the Aikido MCP server is not available or fails, inform the user:

The Aikido MCP server is required for Aikido feed issues but is not available. Install it following the setup guide at reference.md, or run /aikido:setup, then retry.

Source and attribution

Source:AikidoSec/aikido-claude-plugininskills/issuesat commit02f018a

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal