What is cx-cli-setup?

A setup guide for the Checkmarx cx command-line tool, used to run Checkmarx security tasks from a terminal. It covers checking the tool, installing or upgrading it, and signing in when required.

Checking cx availability and version, validating authentication, and bootstrapping installation or setup in bash, Windows Command Prompt, or PowerShell.

It resolves failures caused by a missing, outdated, or unauthenticated cx command before security work can run.

cx-cli-setup — Cursor rule by Checkmarx

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add rules/checkmarx/cx-agentic-ai/cx-cli-setup

Clone the repo

git clone --depth 1 https://github.com/Checkmarx/cx-agentic-ai

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 899 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00027	$0.00899
Opus 5	$0.00014	$0.00449
Sonnet 5	$0.00005	$0.00180
Haiku 4.5	$0.00003	$0.00090

Measured yesterday against content hash c3d818b5722e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cx-cli-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/cursor-devassist/rules/cx-cli-setup.mdc · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CX CLI Setup

Use when cx is missing, below minimum version, incapable, or not authenticated — or when the user runs /cx-cli-setup.

Shell syntax (read first on Windows)

Cursor's Shell tool uses the workspace default shell — PowerShell on Windows. Write every command for the shell you are in; full table in skills/cx-cli-setup/references/shells.md:

	PowerShell	cmd.exe	bash / sh
Run a quoted/absolute path	`& "<path>" args` (`&` required)	`"<path>" args`	`"<path>" args`
Path separator	`\`	`\`	`/`
Discard stdout	`1>$null`	`1>NUL`	`1>/dev/null`
Env var	`$env:LOCALAPPDATA`	`%LOCALAPPDATA%`	`$LOCALAPPDATA`

A bare cx … and bash "<script>" install are identical in all shells. Never chain (;/&&/|), substitute ($(...)/backticks), or redirect to a real file — the gate blocks those.

Entry

Check presence: which cx (bash/sh) · where cx (cmd) · Get-Command cx (PowerShell)
If present: cx auth validate (distinguish credential vs network failures from error text)

CLI	Auth	Action
No	—	Bootstrap install (see deny `agent_message` for exact path)
Yes	OK	Confirm ready; offer reconfigure only if asked
Yes	Credential fail	Phase 2 auth only
Yes	Network fail	Fix network/proxy; do not re-auth

Install

Use the exact bootstrap command from a hook deny agent_message: bash "<resolved-path>/scripts/cx-bootstrap.sh" install
Never substitute ${CURSOR_PLUGIN_ROOT} — it is empty in the agent shell
Ask once: "Install/upgrade Checkmarx CLI now? (Y/n)"

Verify

Invoke cx by canonical absolute path when not on PATH, in your shell's form:
- PowerShell: & "$env:LOCALAPPDATA\Checkmarx\cx\cx.exe"
- cmd.exe: "%LOCALAPPDATA%\Checkmarx\cx\cx.exe"
- bash/sh (Git Bash): "$LOCALAPPDATA/Checkmarx/cx/cx.exe"
- bash/sh (Unix): "$HOME/.checkmarx/bin/cx"
A bare cx returning 127 after first install is expected; trust the next gate deny reason (not authenticated → proceed to auth; not installed → re-run bootstrap)

Read the full file on GitHub · 69 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 69 lines · 27 tokens per session scan A c3d818b5722e

Subscribe to this mod's changes

cx-cli-setup is a cursor rule published in the GitHub repository Checkmarx/cx-agentic-ai (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 899 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Data and AI Security agent ai mcp mcp-server model-context-protocol oauth2

cx-cli-setup

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

CX CLI Setup

Shell syntax (read first on Windows)

Entry

Install

Verify

What this file has done since we first saw it

Other cursor rules, from other repositories

grok-mcp

intelligence-router

frontend-architecture

react_hooks

cursorrules

use-bun-instead-of-node-vite-npm-pnpm