Supply chain investigation, evidence recovery, and forensic analysis for GitHub repositories. Covers deleted commit recovery, force-push detection, IOC extraction, multi-source evidence collection, hypothesis formation/validation, and structured forensic reporting. Inspired by RAPTOR's 1800+ line OSS Forensics system.
67
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Security
2 findings: 1 critical severity, 1 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
Detected a suspicious URL in the skill instructions that could lead the agent to download and execute malicious scripts or binaries. This includes links to executables from untrusted sources, typosquatting of official packages, URL shorteners that obscure the destination, and personal file hosting services.
The majority of listed URLs are GitHub, GitHub API, or Wayback Machine links (low risk), but the presence of a direct .sh downloader hosted on an untrusted domain (https://evil.example.com/payload.sh) is a high-risk indicator of malicious payload distribution.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill explicitly instructs the agent to extract and store API keys/tokens as IOC "Value" (Phase 1) and even shows an example token pattern ("export GITHUB_TOKEN=ghp_..."), which forces the LLM to handle secret values verbatim (despite later advising redaction), creating a high exfiltration risk.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The required workflow fetches outsider-authored content at runtime (e.g., via the Wayback Machine in Investigator 3 and evidence store entries derived from `web_archive` content), and that recovered page text can be carried into `evidence.json` and then into the agent’s LLM context during report generation/summarization.
d92bfa0
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.