sparkBLOCK

CocoPlus is an Agentic Operating System for Snowflake Coco. It brings structured, multi-agent workflows to data engineering projects — covering everything from project initialization through spec, plan, build, test, review, and ship phases.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: "adversary"
description: "Show CocoAdversary reviewer configuration and latest challenge results."
version: "2.0.1"
author: "CocoPlus"
tags:
  - cocoplus
  - cocoadversary
---

Your objective is to implement `$adversary`.

Before proceeding, verify that `.cocoplus/` exists. If not, output: "CocoPlus not initialized in this directory. Run `$pod init` to begin." Then stop.

Read `.cocoplus/modes/adversary.on`, `.cocoplus/adversary/config.json`, and recent adversary reports. Summarize enabled state, configured challenge depth, latest high-severity finding, and known gaps.

Available subcommands: `$adversary enable`, `$adversary disable`, `$adversary run`, `$adversary show`, `$adversary audit`, `$adversary gap`.

## Anti-Rationalization

| Shortcut / Temptation | Why It Fails |
|-----------------------|--------------|
| Treat the skill as complete because the file exists | Skill contracts must describe observable behavior and verification, not just command names. |
| Skip artifact and safety checks for a small command | Small commands still mutate state or guide execution; preserve the same gates. |

## Exit Criteria

- [ ] Command behavior matches the owning feature contract.
- [ ] Required reads, writes, and user-visible outputs are described.
- [ ] Safety, governance, and artifact constraints are preserved.
- [ ] Missing state produces a clear, non-destructive result.

BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (3)

- Security controls (access validation, credential handling, injection defense)

- If the LLM synthesis call fails (access error, timeout, rate limit, credential constraint):

description: "Activate and manage Leviathan God Mode and Ronin companion state. Supports `$leviathan on/off/status/learn`."

Gates applied: no_behavioural_pass.