CC supply-chain-guard
Detect and remediate software supply chain attacks in npm, PyPI, crates.io, GitHub Actions, and CI/CD pipelines by scanning for known compromised packages, malicious versions, filesystem IOCs, C2 indicators, and CI/CD misconfigurations.
Detect and remediate software supply chain attacks in npm, PyPI, crates.io, GitHub Actions, and CI/CD pipelines by scanning for known compromised packages…
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 6
✓ No critical or high findings
Medium and low: 6
-
medium Dangerous commands
cmd-cryptominerreferences/ioc-database.md:53Installs or runs a cryptocurrency miner on the user's machine (documentation of a security skill)| sympy-dev | All versions | N/A (remove, use sympy) | XMRig cryptominer | 2026-01-17 |
security skill -
medium Dangerous commands
cmd-persistencescripts/scan-python.sh:226Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)CRON=$(crontab -l 2>/dev/null || true)
security skill -
low Dangerous commands
cmd-cron-mentionscripts/scan-python.sh:226Mentions editing / listing crontab (documentation of a security skill)CRON=$(crontab -l 2>/dev/null || true)
security skill -
low Risky intent
intent-offensive-securitySKILL.md:87Offensive-security / dual-use content (legitimate for authorised testing; review intended use)5. Check for lateral movement in Kubernetes clusters
-
low Risky intent
intent-offensive-securitySKILL.md:124Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Deploys WAV steganography for payload delivery
-
low Risky intent
intent-offensive-securitySKILL.md:125Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- Targets Kubernetes for lateral movement
detector
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 11 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 65 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1591 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 236: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 65 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.