bugs

Coordinate parallel subagents to identify day-0 security and correctness bugs.

16|3|Updated May 5, 2026
One-click install
npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill bugs-kevin-liu-01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugs
Source: https://github.com/Kevin-Liu-01/Agent-Machines/tree/main/knowledge/skills/bugs
Command: npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill bugs-kevin-liu-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates a parallel bug-hunt to discover day-0 security and correctness flaws by dispatching subagents to audit critical files and surfaces.

Core Features & Use Cases

  • Distributes one hunter per critical file or surface to maximize coverage.
  • Produces a consolidated report with severity, evidence, and suggested remediation paths.
  • Supports honest failure reports when no bug is found to avoid false positives.

Quick Start

Dispatch an Explore pass to map critical files, then launch hunters to audit them.

Frequently Asked Questions about bugs

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

FAQPage Schema
How do I run a parallel security audit to find day-0 vulnerabilities in a codebase?

A parallel security audit dispatches hunter subagents to critical files and attack surfaces, requiring explicit proof of discovered flaws without applying automatic fixes. It coordinates exploration, triage, and reporting to maximize coverage across the codebase.

What is the best way to discover zero-day correctness bugs across multiple modules simultaneously?

Discovering zero-day correctness bugs simultaneously involves dispatching one hunter subagent per critical file or module surface. This parallel approach maximizes coverage and produces a consolidated report with severity levels, evidence, and suggested remediation paths.

Can I use parallel subagents for CTF bug hunting and vulnerability discovery?

Parallel subagents support CTF bug hunting and vulnerability discovery by mapping critical files during an exploration pass, then launching targeted hunters to audit them. They require explicit proof of any identified exploit and report honest failures to avoid false positives.

How do I reproduce security flaws found during a codebase audit without applying automatic fixes?

Reproducing security flaws during a codebase audit requires subagents to provide explicit proof of the vulnerability. The process deliberately avoids automatic fixes, instead producing a triage report with severity, evidence, and suggested remediation paths for manual review.

Does this bug hunting approach report failures when no vulnerability is found?

Yes, the bug hunting approach produces honest failure reports when no bug is found to avoid false positives. This ensures the consolidated report only contains verified security and correctness flaws backed by explicit evidence from the triage process.