third-party-detector

Identify third-party services in web applications using JavaScript, HTML, DNS, HTTP, and job signals.

7|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/ArianHobson333/claude-bug-bounty-stack --skill third-party-detector-arianhobson333
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: third-party-detector
Source: https://github.com/ArianHobson333/claude-bug-bounty-stack/tree/main/vendor/communitytools/projects/pentest/.claude/skills/techstack-identification/third_party_detector
Command: npx skills add https://github.com/ArianHobson333/claude-bug-bounty-stack --skill third-party-detector-arianhobson333

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies third-party services integrated into a target's technology stack, aiding in understanding potential vulnerabilities and dependencies.

Core Features & Use Cases

  • Third-Party Service Identification: Detects payments, analytics, auth, CRM, and support services.
  • Signal Analysis: Reads JavaScript signals, HTML signals, DNS signals, HTTP signals, and job signals.
  • Service Categories: Categorizes services into payment processing, analytics, customer support, authentication, CRM, error monitoring, A/B testing, CDN, media, and social communication.
  • Use Case: Utilize this Skill to identify third-party services during a security audit of a web application.

Quick Start

Run the third-party-detector skill on the target application to automatically identify third-party services.

Frequently Asked Questions about third-party-detector

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

FAQPage Schema
How do I identify third-party services in a web application tech stack?

This Skill detects third-party services by analyzing JavaScript, HTML, DNS, HTTP, and job signals. It categorizes discovered dependencies into groups like payment processing, analytics, and customer support to aid in security audits.

What signals are analyzed during a third-party service security audit?

A third-party service security audit analyzes JavaScript, HTML, DNS, HTTP, and job signals. These signals expose integrated external dependencies, allowing you to map the full technology stack and identify potential vulnerabilities.

Can I detect specific categories of third-party services like payment processing and analytics?

You can detect specific third-party service categories including payment processing, analytics, customer support, authentication, CRM, error monitoring, A/B testing, CDN, media, and social communication through targeted signal analysis.

How do I map external dependencies for a tech stack analysis?

To map external dependencies for tech stack analysis, run this Skill on the target application. It automatically identifies and categorizes integrated third-party services to help understand potential vulnerabilities.

What is the best way to find external integrations during a web application security audit?

To find external integrations during a security audit, analyze JavaScript, HTML, DNS, and HTTP signals. This detects categorized third-party services like authentication and CRM platforms within the tech stack.