BF payment-402
Access protected APIs and digital resources via the x402 "Payment Required" protocol on Base L2. This skill automates cryptographic handshakes and USDC micro-payments to unlock restricted content. Built for "Pay-per-Resource" agentic billing.
As a process F 40/100 · Will not run — References files that are not bundled: @paynodelabs/sdk-js
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 purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.
Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Risky intent
intent-wallet-secretsSKILL.md:25Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target# [REQUIRED] PayNode Burner Wallet Private Key
-
low Secrets in code
secret-high-entropy-tokenreferences/TESTING.md:55High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)- **Router Address**: `0x24…a6F`
fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/TESTING.md:56High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)- **USDC Address**: `0x10…784`
fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/TESTING.md:57High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)- **Merchant Address**: `0x59…C0E` (Treasury for demo)
fixturequoted
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: @paynodelabs/sdk-js - note
frontmatter-keyunknown frontmatter key "required_env_vars" - note
frontmatter-keyunknown frontmatter key "required_binaries" - note
frontmatter-keyunknown frontmatter key "primary_credential" - note
frontmatter-keyunknown frontmatter key "install"
Process rating: all ten parameters 40/100
- 0Tools and files. 1 referenced file(s) missing: @paynodelabs/sdk-js
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 85Steps. 25 steps, 1 vague phrases
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1178 tokens
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- -34 of 4 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 242: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.