oss-forensics-orchestration
Orchestrates multi-agent forensic investigations on public GitHub repositories, coordinating parallel evidence collection, hypothesis formation, verification, and report generation.
62
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/oss-forensics/orchestration/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
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.
Why it was flagged
The workflow spawns multiple investigator agents that at runtime will fetch and ingest outsider-authored free text from public sources (e.g., GH Archive/Wayback/GitHub API and potential vendor report URLs via the “Extract IOCs from vendor report” task), and that ingested text is then summarized and passed through the LLM context in later phases (e.g., the “Evidence summary” fed into `oss-hypothesis-former-agent`).
- Repository
- gadievron/raptor
- Commit
75f6956
- Audited
- Security analysis
Is this your skill?
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.