AB IDOR Vulnerability Testing
This skill should be used when the user asks to "test for insecure direct object references," "find IDOR vulnerabilities," "exploit broken access control," "enumerate user IDs or object references," or "bypass authorization to access other users' data." It provides comprehensive guidance for detecting, exploiting, and remediating IDOR vulnerabilities in web applications.
This skill should be used when the user asks to "test for insecure direct object references," "find IDOR vulnerabilities," "exploit broken access control,"…
As a process B 73/100 · Nearly there — weak spots: consistency, running it twice, progress reporting
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securitySKILL.md:234Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Horizontal privilege escalation (user-to-user) vs vertical (user-to-admin)
-
low Risky intent
intent-offensive-securitySKILL.md:337Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# If accessible: Vertical privilege escalation achieved
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 73/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (IDOR Vulnerability Testing) differs from the folder (idor-testing)
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Execution cost. Instruction body is 3027 tokens
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 373: enough signal without eating the budget
- +4Structure: 48 headings
- +3Step-by-step instructions: 28 items
- +3Output format is stated explicitly
- +4Has examples (26 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.