Adr Writing

Security checks across malware telemetry and agentic risk

Overview

This ADR-writing skill is coherent and only uses narrow local repo inspection, a disclosed numbering helper, and intended ADR file creation.

Install only if you want an agent to inspect local project context and create ADR Markdown files under docs/adrs/. Review the generated ADR and any local file diffs before committing or sharing them.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • 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)

Tp4

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding
This is a clear mismatch. The declared purpose is about authoring, formatting, and quality-checking ADR documents using the MADR template and E.C.A.D.R. criteria. The actual code does none of that: it only inspects the filesystem to find ADR markdown files and compute the next numeric identifier. Its primary purpose is ADR numbering, not ADR writing/formatting/completeness verification. That numbering utility is not mentioned in the description, so the code performs materially different behavior from what is declared.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal