Skip to main content

Overview

The Cysmiq CLI queries scan results, evaluates policy thresholds, updates vulnerability workflow state, and installs official Cysmiq skills for supported coding agents. For task-focused instructions, see Use the CLI in CI/CD and Use the CLI with coding agents.

Prerequisites

  • A Cysmiq workspace slug for workspace-scoped commands
  • A Cysmiq API token with access to the workspace
  • A repository connected to Cysmiq for repository-scoped checks, or an application for application-scoped checks
See API keys to generate an API token.

Installation

Install via Homebrew
Homebrew 6 may require explicit trust for existing installations from non-official taps during upgrades. If Homebrew reports that cysmiq/tap/cysmiq is from an untrusted tap, trust the Cysmiq cask and rerun the upgrade:
Trust the Cysmiq cask
To trust all entries from the Cysmiq tap on managed machines, trust the tap once:
Trust the Cysmiq tap
Verify the installation:
Verify installation

Configuration

The CLI reads configuration from these sources, in order of precedence:
  1. Command-line flags: --base-url, --tenant, --token
  2. Environment variables: CYSMIQ_BASE_URL, CYSMIQ_TENANT, CYSMIQ_TOKEN, and other CYSMIQ_ prefixed options
  3. Config file: ~/.cysmiq/config.yaml

Required settings

Config file

Create ~/.cysmiq/config.yaml to avoid passing common flags repeatedly:
~/.cysmiq/config.yaml
Use hyphenated option names in the config file:
~/.cysmiq/config.yaml
Avoid storing API tokens in the config file. Use CYSMIQ_TOKEN instead.

Commands

List Tenants, Repositories, and Applications

Use the resource list commands to find the workspace, repository, or application identifiers you need for automation.
List accessible workspaces
List repositories in a workspace
List applications in a workspace
tenants list is not workspace-scoped, so it requires only --base-url and --token. repos list and applications list require a workspace through --tenant or CYSMIQ_TENANT. Options: Use --json or --output json when another script or coding agent will consume the result. These commands require the matching API key scopes: tenants:read for tenants list, repositories:read for repos list, and applications:read for applications list. Existing keys keep the scopes selected when they were created, so older keys may need to be recreated with the new scopes.

Run Checks

Use cysmiq check to run a policy check and set the exit code based on vulnerabilities found. Use this in CI/CD pipelines to gate deployments.
Basic check
The check command requires either a repository or an application. In repository mode, provide --ref for the latest known scan on a branch or tag, or --sha for a specific commit. When only --repo is available and inference cannot find a ref or SHA, the CLI uses the repository default branch. When --sha is provided in repository mode, check waits for the scan to reach a terminal state before evaluating the result. Use --poll-interval and --wait-timeout to control how often the CLI checks scan status and how long it waits. Application mode evaluates vulnerabilities across the application’s repositories and does not wait on one scan. Exit codes:
  • 0: Check passed
  • 2: Usage error, invalid flag value, missing required setting, or canceled command
  • 3: Conflict, such as a stale --status-version
  • 4: Unauthorized API token
  • 5: Forbidden API request or token without the required ability
  • 6: Resource not found
  • 7: Scan unavailable for the provided SHA
  • 8: API validation error
  • 9: API or transport error, including failed scan terminal states and wait timeouts after a scan was observed
  • 10: Policy failure because the configured threshold was exceeded
Exit code 1 is reserved for generic shell or runtime failures outside the CLI’s explicit error classes. Options: --poll-interval and --wait-timeout must include a duration unit, such as 5s, 30s, 2m, or 15m. Examples:
Fail only on critical vulnerabilities
Check a specific commit
Check an application
Check a commit with shorter polling
Fail if more than 10 vulnerabilities
JSON output for parsing

List Vulnerabilities

Use cysmiq vulns list to list vulnerabilities for a repository or application. By default, the CLI returns open, confirmed vulnerabilities and renders them as cards.
List open vulnerabilities
Options:
List critical vulnerabilities across all pages
List vulnerabilities for an application
List vulnerabilities assigned to you
Export as JSON
Export selected JSON fields

Get Vulnerability Details

Use cysmiq vulns get to get details for one vulnerability.
Get vulnerability details
Options:
Get selected fields
Include locations and advisory details

List Vulnerability Locations

Use cysmiq vulns locations to list locations for one vulnerability.
List vulnerability locations
Options:
List live locations as a table

Assign Vulnerabilities

Use cysmiq vulns assign to assign a vulnerability to a user.
Assign to yourself
Options:

Clear Vulnerability Assignees

Use cysmiq vulns unassign to clear the assignee on a vulnerability.
Clear assignee
Options:

Triage Vulnerabilities

Use cysmiq vulns triage to change vulnerability triage state.
Mark a vulnerability as accepted
Use ignored when the finding is a false positive. Options:

Summarize Vulnerabilities

Use cysmiq vulns summary to show a vulnerability count summary without listing individual items.
Show vulnerability summary
Show application vulnerability summary
vulns summary supports the same vulnerability filter fields as vulns list, except pagination, assignee, color, and field projection.

Show Version

Use cysmiq version to print version information.
Show version

Update CLI

Use cysmiq update to update the CLI to the latest version.
Update to latest
Check for updates

Agent Skills

Use cysmiq skills to install and manage official Cysmiq skills for coding agents. Skills are local files, so installs and updates preserve local edits unless you explicitly choose an overwrite option. Supported agent IDs: List the available skills bundle:
List available skills
Install the Cysmiq skill for Codex in the current project:
Install for Codex
Install for every supported agent in the current project:
Install for all supported agents
Check what is installed and whether it is current:
Check installed skills
Diagnose local skill setup:
Diagnose skill setup
Update installed skills:
Update installed skills
Remove installed Cysmiq skills:
Remove installed skills
Scopes: Options: skills update replaces official files that still match the installed version. Locally modified Cysmiq-owned files require --backup or --force. skills remove removes Cysmiq-owned files and leaves unrelated local files in place.

Global options

These options apply to all commands:

Shared vulnerability filters

These options apply to check, vulns list, and vulns summary unless a command table states otherwise. When --state is omitted, the CLI sends open. Use --state all to request all workflow states. --ref and --sha require repository mode. Use --application when you want to evaluate or list vulnerabilities across all repositories in an application.