advanced-github-security-scanner

Discover confirmed GitHub repository files and generate verified security findings.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mickdarling/dollhouse-portfolio --skill advanced-github-security-scanner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: advanced-github-security-scanner
Source: https://github.com/mickdarling/dollhouse-portfolio/tree/main/skills
Command: npx skills add https://github.com/mickdarling/dollhouse-portfolio --skill advanced-github-security-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates false positives and broken links by discovering and validating actual repository files before performing security checks, ensuring automated URLs point to real content. It integrates with the dollhouse security framework to validate code, dependencies, and configurations across real files only.

Core Features & Use Cases

  • Smart file discovery: identifies files that actually exist by querying the repository search results and confirming their presence.
  • Verified URL generation: creates raw.githubusercontent URLs only for files that are confirmed to exist.
  • Reality-based project analysis: detects project type and security mappings from the actual set of confirmed files.
  • Use Case: scan a GitHub repo to obtain a verified security report with trusted URLs and minimized 404s.

Quick Start

Activate the skill and run verification on a GitHub repository: activate skill: advanced-github-security-scanner analyze with verification: https://github.com/OWNER/REPO

Frequently Asked Questions about advanced-github-security-scanner

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

FAQPage Schema
How do I scan a GitHub repository for security vulnerabilities without getting false positives?

GitHub repository security validation eliminates false positives by discovering actual files and generating verified raw.githubusercontent URLs before analysis, ensuring security checks run only on real content. This approach minimizes 404s and broken links.

What is reality-based security analysis for GitHub repos?

Reality-based security analysis validates actual repository files through search queries before generating security findings, avoiding speculative paths. It confirms file existence and creates raw URLs only for verified content, producing trusted remediation guidance.

How do I verify GitHub file URLs to avoid broken links in automated security reports?

Verified URL generation queries repository search results to confirm file presence before creating raw.githubusercontent URLs. This phase-driven workflow ensures all generated links point to real content, eliminating 404 errors in security reports.

Can I automate GitHub security scanning with real file discovery instead of speculative paths?

Automated security scanning uses real file discovery to identify files that actually exist by querying repository search results and confirming their presence. No speculative paths are required, and results return only for validated files.

What's the best way to detect project type and security mappings from a GitHub repo's actual files?

Reality-based project analysis detects project type and security mappings from the actual set of confirmed files discovered in the repository. This automated detection runs after file verification, ensuring mappings reflect true repository content.

Does this GitHub security scanner work without dependencies or external components?

The GitHub security scanner operates with no dependencies and no external components, using a self-contained phase-driven workflow. It discovers files, generates URLs, and analyzes security independently within the dollhouse security framework.