AF lance
Web3 bug bounty and protocol security agent for evidence-backed vulnerability discovery and reporting. Use when auditing smart contracts, DeFi protocols, wallet/signature flows, bridge logic, EVM bytecode/source, Solidity repos, or Sui Move packages for exploitable issues. Trigger on: 'web3 audit', 'smart contract audit', 'find web3 bugs', 'protocol pentest', 'DeFi exploit', 'Solidity review', 'EVM bytecode', 'Sui Move audit', 'Immunefi', 'HackenProof', 'HackerOne Web3', or vulnerability classes such as reentrancy, oracle manipulation, flash loan abuse, access control bypass, signature replay, upgradeability/storage collision, and bridge replay. Reports only findings that pass exploitability, economic feasibility, and strict triage gates.
Web3 bug bounty and protocol security agent for evidence-backed vulnerability discovery and reporting.
As a process F 63/100 · Will not run — References files that are not bundled: references/platforms/*.md
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Risky intent
intent-offensive-securityREADME.md:27Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Lance is an Agent Skill for Web3 bug bounty and protocol auditing workflows focused on triage-grade findings. It is built to minimize false positives, force exploitability proof, and require economic
-
low Risky intent
intent-offensive-securityreferences/severity-guide-web3.md:22Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- reliable unauthorized privilege escalation
-
low Risky intent
intent-offensive-securitySKILL.md:11Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)description: "Web3 bug bounty and protocol security agent for evidence-backed vulnerability discovery and reporting. Use when auditing smart contracts, DeFi protocols, wallet/signature flows, bridge l
detector -
low Risky intent
intent-offensive-securitySKILL.md:32Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- bug bounty scope file
-
low Risky intent
intent-offensive-securitySKILL.md:106Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- Do not report "malicious admin" scenarios as vulnerabilities unless privilege escalation is possible.
detector
Files scanned: 51. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/platforms/*.md
Process rating: all ten parameters 63/100
- 0Tools and files. 1 referenced file(s) missing: references/platforms/*.md
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 43 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1409 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)
- +2Single-language instructions
- +3Description length 748: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 43 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
- +3All 6 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.