AC obekt-security
Basic threat detection and security analysis for code, files, and agent skills. Use when you need to scan for vulnerabilities, validate security patterns, detect malicious patterns, or audit codebases for security issues.
Basic threat detection and security analysis for code, files, and agent skills.
As a process C 50/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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 · 9
✓ No critical or high findings
Medium and low: 9
-
low Secrets in code
secret-high-entropy-tokenreferences/CRYPTO_SECURITY.md:254High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)'0x7a…88D',
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/CRYPTO_SECURITY.md:256High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)'0xA0…B48',
quoted -
low Dangerous commands
cmd-eval-dynamicreferences/REMEDIATION_GUIDE.md:16Dynamic code execution from decoded/untrusted input (documentation of a security skill)os.system(f"ls {user_path}")security skill -
low Dangerous commands
cmd-eval-dynamicreferences/VULNERABILITY_PATTERNS.md:26Dynamic code execution from decoded/untrusted input (documentation of a security skill)os.system("mkdir " + user_path)security skill -
low Secrets in code
secret-password-literalreferences/VULNERABILITY_PATTERNS.md:99Hard-coded password / key literal (may be an example)API_KEY = "sk_l…456"
-
low Risky intent
intent-wallet-secretsscripts/secret_scan.py:126Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (detector / deny-list definition)"description": "Ethereum/Wallet private key (64 hex chars)"
detector -
low Risky intent
intent-wallet-secretsscripts/secret_scan.py:129Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)"type": "Mnemonic/Seed Phrase",
quoted -
low Risky intent
intent-wallet-secretsscripts/secret_scan.py:132Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (detector / deny-list definition)"description": "Potential BIP39 mnemonic phrase (12+ words)"
detector -
low Risky intent
intent-offensive-securitySKILL.md:303Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Penetration testing
Files scanned: 10. 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 50/100
- 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
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 111 steps, 2 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2286 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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)
- +1No license
- +2Single-language instructions
- +3Description length 221: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 111 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.