cx-devassist-asca

Scans source code files with Checkmarx ASCA SAST and remediates findings via the Checkmarx MCP tool.

2|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/Checkmarx/cx-agentic-ai --skill cx-devassist-asca-checkmarx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cx-devassist-asca
Source: https://github.com/Checkmarx/cx-agentic-ai/tree/main/plugins/cursor-devassist/skills/cx-devassist-asca
Command: npx skills add https://github.com/Checkmarx/cx-agentic-ai --skill cx-devassist-asca-checkmarx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It detects SAST security vulnerabilities in source code files (.py, .js, .java, .go, .ts, and similar) using the Checkmarx ASCA engine and applies deterministic, MCP-generated fixes instead of ad-hoc manual edits. ## Core Features & Use Cases - On-demand ASCA scanning: Run cx scan asca on a source file and report each finding with rule name, severity, line, description, and remediation advice. - MCP-only remediation: Every fix comes from the mcp__plugin-cx-devassist-Checkmarx__codeRemediation tool; if the MCP is unavailable, the flow stops and recovers the connection rather than improvising a fix. - Scoped re-scan and suppression: After fixing, re-scan the file, remediate only findings tied to your own changes, and optionally suppress confirmed false positives with cx ignore-vulnerability. - Use Case: A hook denies a Write because of a SQL injection finding in app.py; the skill skips re-scanning, calls the remediation MCP, applies the fix at the problematic line, re-scans, and reports a structured remediation summary. ## Quick Start Ask the assistant to scan a source file for security vulnerabilities, for example: scan app.py for security issues and fix any findings.

Frequently Asked Questions about cx-devassist-asca

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan a source file for vulnerabilities with Checkmarx ASCA?

Run `cx scan asca -s "<file-path>"` using the cx CLI's canonical absolute path for your shell. The scan returns JSON findings with rule name, severity, line number, description, and remediation advice for each vulnerability.

What is the difference between ASCA SAST scanning and SCA scanning?

ASCA scans source code files (.py, .js, .java, .go, .ts) for code-level vulnerabilities using SAST. SCA targets dependency manifests and lockfiles like package.json, requirements.txt, or go.mod, and is handled by the separate cx-devassist-sca skill.

Can I remediate Checkmarx findings without the MCP server?

No. All remediation must come from the mcp__plugin-cx-devassist-Checkmarx__codeRemediation tool. If the MCP is unavailable, the flow stops, verifies authentication with `cx auth validate`, and asks you to reload the Cursor window before retrying.

Why does the ASCA re-scan show findings I did not fix?

The scan reads the whole file, so it reports pre-existing findings in code you never touched. Only findings matching your own changes are remediated; the rest are reported as out-of-scope and left unmodified.

How do I suppress a false positive ASCA finding?

Use `cx ignore-vulnerability --scan-type asca --data` with a JSON payload containing FileName, Line, and RuleID. Quote the JSON per your shell's rules, run one command per finding, and retry the blocked write after suppression succeeds.