PulseMon

• Outcome: Pass
• Latest audit: May 29, 2026 at 8:13 PM UTC
• Version:
  1.0.2

Overview

This is a straightforward PulseMon integration that uses a disclosed API key to manage monitoring resources, with some operational actions users should review carefully.

Install only if you are comfortable giving your agent a PulseMon API key and allowing it to change monitor configuration. Review update, pause, resume, and delete requests before approving them, and do not put secrets, tokens, or sensitive job output in ping bodies because they may appear in alerts.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (4)

Vague Triggers

Medium

• Confidence: 84% confidence
• Finding: The README advertises very broad natural-language commands such as checking, creating, updating, deleting, pausing, and pinging monitors with no indication of scoped invocation, confirmation, or safeguards. In an agent setting, these phrases can plausibly overlap with ordinary user conversation and lead to unintended execution of operational actions, including state changes and deletions.

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: The README explicitly promotes monitor deletion through natural language but provides no warning that deletion is destructive and no mention of confirmation or recovery behavior. In an agent-integrated environment, this increases the risk that a casual or ambiguous instruction could irreversibly remove monitoring coverage and blind operators to cron/job failures.

Missing User Warnings

Low

• Confidence: 78% confidence
• Finding: The README instructs users to generate and export an API key but does not warn that the credential is sensitive or advise against exposing it in logs, screenshots, prompts, or source control. While this is common setup documentation, omission of basic secret-handling guidance increases the chance of accidental credential leakage and unauthorized API access.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The skill explicitly documents a ping body field and notes it is included in alert notifications, but it does not warn users not to place secrets, tokens, credentials, or sensitive job output there. In a monitoring context, job output often contains stack traces, identifiers, and operational data, so encouraging or normalizing arbitrary body submission can lead to unintended sensitive-data disclosure through alerts and downstream notification channels.

VirusTotal

66/66 vendors flagged this skill as clean.