Rails CI Fixer

Security checks across malware telemetry and agentic risk

Overview

This is a disclosed Rails CI repair workflow with real repository and GitHub-token risk, but the access fits its purpose and includes human approval gates.

Install only if you want an agent to actively repair Rails CI on repositories you own and trust. Use a fine-grained GitHub token limited to the target repo, review diffs before approving commits, and use an isolated environment for unfamiliar codebases.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Vague Triggers

Medium
Confidence
90% confidence
Finding
The trigger phrases include very common developer language such as "fix CI", "CI is failing", and "the build is broken", which can cause the skill to activate in ordinary conversation rather than through deliberate invocation. In this skill, unintended activation is more dangerous because the workflow encourages accessing GitHub Actions logs, running repository code via RSpec, and preparing code changes, all of which increase the chance of acting on an untrusted repo or at the wrong time.

VirusTotal

62/62 vendors flagged this skill as clean.

View on VirusTotal