Document --fail-on malicious in the agent skill - #136
Merged
Conversation
`corgea scan --fail-on malicious` shipped in #125 (COR-1647) and is on the docs site, but the agent-facing skill contract only showed `--fail-on CR`. Agents reading the skill had no way to discover the malicious condition — the only gate covering ecosystems the npm/pip install wrappers do not. Add the examples, the accepted-condition list matching the clap help text, and a CI/CD example combining severity with malicious.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
No actionable findings. I verified the merge-base diff is limited to skills/corgea/SKILL.md; the documented malicious token, comma-separated OR behavior, at-or-above severity semantics, scan-scoped SCA classification, and CI example all match src/main.rs, src/scanners/blast.rs, and the public CLI documentation. The focused gate implementation already covers single/mixed tokens and malicious-only behavior, git diff --check is clean, and the PR's rust-tests check passes. There were no prior review threads on this PR to reconcile.
Sent by Cursor Automation: pr-flow
leenk7991
approved these changes
Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
corgea scan --fail-on maliciousshipped in #125 (COR-1647) and is documented on the docs site, butskills/corgea/SKILL.md— the agent-facing contract — only ever showed--fail-on CR. An agent reading the skill had no way to know the malicious condition exists.That matters for the supply-chain story: the scan gate is the only surface that blocks malicious dependencies in ecosystems the
corgea npm/corgea pipinstall gate does not cover (Maven, NuGet).Changes
--fail-on maliciousand--fail-on HI,malicious.--fail-onhelp text inmain.rs.malicious.Docs only — no behavior change.
./harness checkpasses, including the deps skill drift check.