Agent Migration & Versioning: Blue-Green Deployments, Canary Releases, and Rollback Strategies for AI Agent Commerce

• Outcome: Review
• Latest audit: May 29, 2026 at 9:33 PM UTC
• Version:
  1.3.1

Overview

This non-executable guide is coherent, but it includes run-as-is live GreenHelix migration code that can change financial agent state despite an earlier sandbox-only notice.

Review carefully before using the examples. Treat the code as production-capable, not just sandbox documentation. Use a sandbox endpoint and least-privilege GreenHelix key first, and require explicit human approval before running anything that changes budgets, cancels escrows, rotates keys, registers services, migrates state, or rolls back live agents.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access

Findings (3)

Intent-Code Divergence

Medium

• Confidence: 91% confidence
• Finding: The guide claims examples use a sandbox and do not require an API key, but later includes runnable code targeting the live production API. This mismatch can mislead users into executing production-affecting operations under the assumption they are safe examples, increasing the chance of accidental real-world changes to financial agent state.

Intent-Code Divergence

High

• Confidence: 98% confidence
• Finding: The documented guidance correctly says to verify the new API key in production before revoking the old one, but the implementation revokes the source key immediately after creating a new key. This can cause authentication outages or failed migrations, and in a financially active agent system that can interrupt settlement, escrow handling, and rollback operations.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The live-execution section tells users to install the library, set an API key, and run the code as-is against the live GreenHelix API, but it does not clearly warn that the code performs production-affecting actions. Users may unknowingly trigger service registration changes, budget freezes, escrow cancellation, rollback, or state migration against real systems.

VirusTotal

66/66 vendors flagged this skill as clean.