Audit external GitHub repositories for security risks before integration.
npx skills add https://github.com/0xUrsanomics/utopia-os --skill repo-audit-0xursanomics
Please help me install this Agent Skill. Skill: repo-audit Source: https://github.com/0xUrsanomics/utopia-os/tree/main/skills/repo-audit Command: npx skills add https://github.com/0xUrsanomics/utopia-os --skill repo-audit-0xursanomics
This Skill prevents the accidental adoption of malicious or insecure software by enforcing a rigorous, security-first triage process before any external code is integrated into your environment.
Use the repo-audit skill to evaluate the safety and utility of the repository at https://github.com/owner/repo.
High-intent search queries and answers about installing and using this skill.
To audit a GitHub repository for supply-chain attacks, perform a security-focused triage that verifies repository age, provenance, and license validity, followed by manual source-code inspection to detect telemetry or credential-stealing hooks before installation.
The best way to triage external libraries for security risks is to apply a structured evaluation process that assesses the repository's blast radius and enforces strict security gates, yielding a decision to doc-mine, clone-audit, install-direct, or park the tool.
To check if a new GitHub tool contains malicious code or credential-stealing hooks, conduct a manual source-code inspection during triage to identify suspicious telemetry, unauthorized network calls, or credential exfiltration attempts in high-risk components.
You need to perform a source-level audit on external repositories when evaluating new tools, libraries, or agentic workflows before integrating them into a secure environment to prevent the accidental adoption of insecure software.
Yes, repo-audit works for evaluating agentic workflows and new tools by applying strict security criteria, including age verification and provenance checks, to determine if the external code is safe to install in your environment.
Automated security triage for external repositories is limited by the necessity of manual source-code inspection for high-risk components, meaning automated checks alone cannot fully guarantee safety without human verification of complex code paths.
openshift-engList actionable open pull requests from GitHub repositories using the GitHub CLI and jq.
ybbms777Classify tool-call risk levels and suggested actions before execution.
jasonwilmotPlan code refactors with blast-radius analysis and rollback strategies.
OWASPDetect hardcoded secrets in source code and configuration files.
