CD senior-secops
SecOps for application security, vulnerability management, compliance, and secure development. Use when implementing security controls, conducting security audits, responding to vulnerabilities, or meeting compliance requirements.
SecOps for application security, vulnerability management, compliance, and secure development.
As a process D 47/100 · Unfinished process — References files that are not bundled: references/*.md
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
- The text references files that are not there: add them or drop the references.
- 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-eval-dynamicassets/sample_app_flawed/app.py:29Dynamic code execution from decoded/untrusted inputos.system("ls " + u) -
low Risky intent
intent-offensive-securityreferences/compliance_requirements.md:59Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] Penetration testing (annual)
-
low Dangerous commands
cmd-eval-dynamicreferences/security_standards.md:105Dynamic code execution from decoded/untrusted input (documentation of a security skill)# NEVER use: os.system(f"ping {user_input}")security skill -
low Risky intent
intent-offensive-securityreferences/standards-and-playbook.md:78Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Req 11 | Security testing (SAST, DAST, penetration testing) |
-
low Secrets in code
secret-password-literalreferences/standards-and-playbook.md:106Hard-coded password / key literal (may be an example) (placeholder value)API_KEY = "sk-1…def"
placeholder -
low Risky intent
intent-offensive-securitySKILL.md:93Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Penetration testing execution or red-team operations -- these require specialized tooling and authorized human operators.
Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/*.md
Process rating: all ten parameters 47/100
- 0Tools and files. 1 referenced file(s) missing: references/*.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 55Failures and branches. 1 branches
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2015 tokens
- 100Running it twice. No mutating operations
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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 230: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 26 items
- +4Reference files are cited in the instructions (5 of 5)
- +3All 3 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.