sunilgentyala

VigilAgent — Security skill for Claude Code

Security community

Security auditing CLI for AI-agent-authored code changesets: detects package hallucinations, indirect prompt injection, and AI-specific code defects before they hit production.

How to install VigilAgent

This entry records only its repository, not the path inside it, so there is no exact command to give. Open sunilgentyala/VigilAgent and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What VigilAgent does

Security auditing CLI for AI-agent-authored code changesets: detects package hallucinations, indirect prompt injection, and AI-specific code defects before they hit production.

Alternatives in Security

  • Security Guardian — Comprehensive security analysis for RTK CLI tool, focusing on command injection, shell escaping, hook security 11.9k ★
  • Promptmap — Security scanner for custom LLM apps 1.2k ★
  • Agentseal — Security toolkit for AI agents 344 ★

README

VigilAgent

[![CI](https://github.com/sunilgentyala/VigilAgent/actions/workflows/ci.yml/badge.svg)](https://github.com/sunilgentyala/VigilAgent/actions/workflows/ci.yml) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) [![Node.js](https://img.shields.io/badge/node-%3E%3D18.0.0-brightgreen)](package.json) [![Docs](https://img.shields.io/badge/docs-live-blue)](https://sunilgentyala.github.io/VigilAgent/) [![Changelog](https://img.shields.io/badge/changelog-0.1.1-informational)](CHANGELOG.md)

Security auditing CLI for AI-agent-authored code changesets: diffs produced by Claude Code, Cursor, Copilot Workspace, and similar coding agents.

VigilAgent reads a unified diff and runs three security-focused detectors that none of the existing terminal diff/review tools cover, then renders the findings as colored terminal output, JSON, or Markdown, with an optional CI exit-code gate.

Why VigilAgent

Terminal diff and review tools have converged on visualization and review ergonomics, not security. Agent-oriented diff viewers make it easier to follow what an agent changed, but they don't audit content. Structural and syntax-highlighting tools render diffs beautifully but perform no security checks at all. "AI slop" scanners catch style and dead-code smells, such as narrative comments and oversized functions, not security defects.

VigilAgent is the layer none of them are: a detector built specifically for the failure modes that show up when an agent, not a human, authored the change. It closes four gaps that are specific to AI-agent-authored code:

  1. Package hallucination: coding agents occasionally invent plausible-sounding package names that don't exist on the real registry, or get talked into adding a typosquatted lookalike. Nothing cross-checks newly added package.json / requirements.txt / Cargo.toml entries against the live npm/PyPI/crates.io registries.
  2. Indirect prompt injection in generated code: an agent