BF pay-with-any-token
Pay HTTP 402 payment challenges using tokens via the Tempo CLI and Uniswap Trading API. Use when the user encounters a 402 Payment Required response, needs to fulfill a machine payment, mentions "MPP", "Tempo payment", "pay for API access", "HTTP 402", "x402", "machine payment protocol", "pay-with-any-token", "use tempo", "tempo request", or "tempo wallet".
As a process F 60/100 · Will not run — References files that are not bundled: ../swap-integration/SKILL.md
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 skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 11
✓ No critical or high findings
Medium and low: 11
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bash(curl:*)allowed-tools: Read Glob Grep Bash(curl:*) Bash(jq:*) Bash(cast:*) Bash(tempo:*) Bash(*/.local/bin/tempo:*) WebFetch AskUserQuestion
-
low Secrets in code
secret-high-entropy-tokenreferences/trading-api-flows.md:24High-entropy token-like string (may be an id, hash or a credential)# Ethereum (1): 0xC0…Cc2
-
low Secrets in code
secret-high-entropy-tokenreferences/trading-api-flows.md:26High-entropy token-like string (may be an id, hash or a credential)# non-zero in the swap response. The ETH sentinel 0xEe…EEE
-
low Secrets in code
secret-high-entropy-tokenreferences/trading-api-flows.md:28High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)USDC_E_ADDRESS="0x83…913" # USDC on Base — update for other chains (see Key Addresses)
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/trading-api-flows.md:79High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)> `0x83…913`. For Ethereum (chain 1), use
detector -
low Secrets in code
secret-high-entropy-tokenreferences/trading-api-flows.md:80High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)> USDC: `0xA0…B48`. See Key Addresses section.
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:204High-entropy token-like string (may be an id, hash or a credential)cast call 0x83…913 \
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:344High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDC.e on Tempo**: `0x20…b50`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:348High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDC on Base (8453)**: `0x83…913`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:349High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDbC on Base (8453)**: `0xd9…6CA`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:350High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDC on Ethereum (1)**: `0xA0…B48`
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../swap-integration/SKILL.md
Process rating: all ten parameters 60/100
- 0Tools and files. 1 referenced file(s) missing: ../swap-integration/SKILL.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 1 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 59 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3690 tokens
- 100Progress reporting. Reports progress
- 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 359: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 59 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.