repo-scout

Security checks across malware telemetry and agentic risk

Overview

This skill is a repository research helper; its GitHub authentication request fits the purpose, but users should handle tokens carefully.

Install is reasonable for GitHub repository scouting. Authenticate locally with GitHub CLI where possible, do not paste tokens into chat or generated files, and use a fine-grained token with the narrowest read access needed, especially if private repositories are involved.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The skill explicitly asks the user to provide a GitHub token and even suggests setting it via an environment variable, but it does not warn that the token is a sensitive credential, recommend least-privilege scopes, or instruct the user not to paste it into chat/output files. In an agent setting, this increases the risk of credential disclosure through conversation logs, terminal history, generated artifacts, or over-broad token use, especially because the skill may access private repository data.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal