aikido-triage

Triage Aikido CSV security findings against a local codebase.

99|10|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/0x0pointer/agent-smith --skill aikido-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aikido-triage
Source: https://github.com/0x0pointer/agent-smith/tree/main/skills/aikido-triage
Command: npx skills add https://github.com/0x0pointer/agent-smith --skill aikido-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the tedious and time-consuming process of triaging security findings from Aikido, ensuring that each finding is accurately assessed against your codebase.

Core Features & Use Cases

  • Automated Triage: Analyzes Aikido security findings (CSV export) against a local codebase.
  • Verdicting: Automatically assigns 'KEEP OPEN' or 'CLOSE' verdicts with specific reasons (e.g., False Positive, Not Exploitable).
  • Evidence Generation: Produces a reviewed CSV and a self-contained HTML evidence report for clear documentation.
  • Use Case: After a penetration test, you receive a CSV export of security findings from Aikido. Instead of manually reviewing each one, you run this Skill to get an immediate, evidence-backed triage report.

Quick Start

Use the aikido-triage skill to review the findings in '~/Downloads/aikido-findings.csv' against the codebase at '/app/my-project'.

Frequently Asked Questions about aikido-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate triaging security findings from a CSV export against my local codebase?

Automated security triage reads flagged files directly from your CSV export, traces code paths locally, and assigns evidence-backed KEEP OPEN or CLOSE verdicts for each finding.

Can I automatically close false positive SAST and SCA findings without manually checking the code?

Yes, SAST and SCA findings are assessed against local code paths to identify false positives, outputting a reviewed CSV with specific verdicts like Not Exploitable for automatic closure.

What is the best way to generate an HTML evidence report for leaked secrets and EOL findings?

Triage your leaked secrets and EOL findings using specific investigation playbooks, which produce a self-contained HTML evidence report detailing the exact code path and verdict.

Does this triage process work with any CSV export or only Aikido security findings?

The triage process is specifically designed to parse Aikido CSV exports, matching flagged files to your local codebase to investigate SAST, SCA, leaked secrets, and EOL findings.

How do I review Aikido pentest findings quickly after receiving an export file?

Run the triage against your Aikido CSV export and local codebase path to immediately generate a reviewed CSV and an HTML report with evidence-backed verdicts for every finding.