AD patch-diff-exploit
Locate vulnerability fixes in vendor patches, diff binaries across versions, and build N-day PoCs. Attack-side complement to binary-diff for authorized research.
Locate vulnerability fixes in vendor patches, diff binaries across versions, and build N-day PoCs.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Risky intent
intent-offensive-securitySKILL.md:48Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (documentation table row)| 把 1-day 武器化部署到目标网络 | `pentest-tools/network-attack-defense/` |
table -
low Risky intent
intent-offensive-securitySKILL.md:211Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- **法律边界** — 武器化 N-day 必须在授权范围内(SRC / Bug Bounty / 自有靶机 / CTF)。对生产环境直接打 1-day 等同入侵
-
low Dangerous commands
cmd-execpolicy-bypassSKILL.md:242Runs PowerShell with execution policy bypassed (documentation of a security skill)powershell -NoProfile -ExecutionPolicy Bypass -File "<SKILL_ROOT>\skills\scripts\boot…ps1" -Capability @('bindiff','ghidriff','ghidra','wsuspect-proxy') -StartServicessecurity skill -
low Risky intent
intent-offensive-securitySKILL.md:261Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)- `pentest-tools/network-attack-defense/` — 把 N-day 武器化部署到目标网络(包装成可投递载荷、对接 C2)
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_repo" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "license_source"
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 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
- 60Tools and files. Uses tools (git, python) that frontmatter does not declare
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2269 tokens
- 100Running it twice. No mutating operations
- 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 161: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.