BF security-reviewer
Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevSecOps practices, cloud security reviews.
Invoke for SAST scans, penetration testing, DevSecOps practices, cloud security reviews.
As a process F 39/100 · Will not run — References files that are not bundled: references/sast-tools.md, references/vulnerability-patterns.md, references/secret-scanning.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 asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 12
✓ No critical or high findings
Medium and low: 12
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Grep Glob Bash
-
low Risky intent
intent-offensive-securitypenetration-testing.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)# Penetration Testing
fixture -
low Risky intent
intent-offensive-securitypenetration-testing.md:44Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)# Privilege escalation
fixture -
low Risky intent
intent-offensive-securitypenetration-testing.md:104Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)### Privilege Escalation (Linux)
fixture -
low Risky intent
intent-offensive-securitypenetration-testing.md:121Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)### Lateral Movement
fixture -
low Risky intent
intent-offensive-securitypenetration-testing.md:131Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)# Credential harvesting
fixture -
low Secrets in code
secret-aws-keysecret-scanning.md:62AWS access key ID (placeholder value)| AWS Access Key | `AKIA[0-9A-Z]{16}` | AKIA…PLE |placeholder -
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)description: Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevSecOps practices, cloud secur
detector -
low Risky intent
intent-offensive-securitySKILL.md:9Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- penetration test
-
low Risky intent
intent-offensive-securitySKILL.md:24Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Security analyst specializing in code review, vulnerability identification, penetration testing, and infrastructure security.
-
low Risky intent
intent-offensive-securitySKILL.md:28Offensive-security / dual-use content (legitimate for authorised testing; review intended use)You are a senior security analyst with 10+ years of application security experience. You specialize in identifying vulnerabilities through code review, SAST tools, active penetration testing, and infr
-
low Risky intent
intent-offensive-securitySKILL.md:32Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)Code review, SAST, vulnerability scanning, dependency audits, secrets scanning, penetration testing, reconnaissance, infrastructure/cloud security audits, DevSecOps pipelines, compliance automation.
detector
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/sast-tools.md - warning
missing-refreference to a missing file: references/vulnerability-patterns.md - warning
missing-refreference to a missing file: references/secret-scanning.md - warning
missing-refreference to a missing file: references/penetration-testing.md - warning
missing-refreference to a missing file: references/infrastructure-security.md - warning
missing-refreference to a missing file: references/report-template.md - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "role" - note
frontmatter-keyunknown frontmatter key "scope" - note
frontmatter-keyunknown frontmatter key "output-format"
Process rating: all ten parameters 39/100
- 0Tools and files. 6 referenced file(s) missing: references/sast-tools.md, references/vulnerability-patterns.md, references/secret-scanning.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (security-reviewer) differs from the folder (pentest)
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 29 steps
- 100Execution cost. Instruction body is 808 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 199: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 29 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.