jxscout-findings

Create, retrieve, and list structured security research findings with deduplication and filtering.

11|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill jxscout-findings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jxscout-findings
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/web-security/skills/jxscout-findings
Command: npx skills add https://github.com/dreadnode/capabilities --skill jxscout-findings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security researchers, bug bounty hunters, and red teamers often track vulnerabilities, exploit gadgets, and security-relevant discoveries in ad-hoc notes or disconnected tools, making it hard to maintain a consistent, searchable record of findings tied to their assessment work. This Skill integrates with jxscout to provide a structured, centralized way to document and manage all security discoveries.

Core Features & Use Cases

  • Structured Finding Creation: Log confirmed vulnerabilities, useful exploit gadgets, security misconfigurations, and sensitive data exposures with custom severity levels, descriptive categories, and structured metadata.
  • Finding Management: List, filter, and paginate existing findings by severity or kind, and retrieve full details of specific findings for review or reporting.
  • Use Case: A bug bounty hunter discovers a stored XSS vulnerability on a user profile endpoint, uses the Skill to create a high-severity finding with a detailed description, deduplication key, and metadata linking to captured HTTP evidence, then later filters all critical and high findings to prioritize their report submissions.

Quick Start

Use the jxscout-findings skill to create a high-severity finding for a stored XSS vulnerability on the /api/user-profile endpoint with a description of the impact and relevant metadata linking to captured request evidence.

Frequently Asked Questions about jxscout-findings

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

FAQPage Schema
How do I track security findings during a bug bounty hunt?

To manage security findings, you can log confirmed vulnerabilities and misconfigurations with deduplication keys, severity levels, and structured metadata. This allows you to list, filter by severity or kind, and paginate existing findings to prioritize report submissions.

Can I filter tracked vulnerabilities by severity for red teaming reports?

Yes, you can filter security findings by severity or kind to isolate critical and high-severity discoveries. This helps prioritize report submissions by retrieving full details of specific findings and listing existing records with pagination.

How do I document exploit gadgets and link them to HTTP evidence?

You document exploit gadgets by creating structured findings and attaching structured metadata. This metadata ties your security findings directly to affected assets and captured HTTP evidence, replacing disconnected tracking tools with a centralized, searchable record.

What is the best way to deduplicate security vulnerabilities discovered during application security assessments?

The best way to deduplicate security vulnerabilities is to assign a deduplication key during structured finding creation. This prevents duplicate tracking of security discoveries across application security assessments by maintaining a consistent, centralized record.