BC agent-economy
x402 payment layer for AI agents — charge USDC per skill call. Meta-skill that wraps any skill with per-call pricing and on-chain payment verification.
As a process C 55/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
For the model run — optional
- 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 · 8
✓ No critical or high findings
Medium and low: 8
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:195High-entropy token-like string (may be an id, hash or a credential)| Base | 8453 | 0x83…913 |
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:196High-entropy token-like string (may be an id, hash or a credential)| Ethereum | 1 | 0xA0…B48 |
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:197High-entropy token-like string (may be an id, hash or a credential)| Polygon | 137 | 0x3c…359 |
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:198High-entropy token-like string (may be an id, hash or a credential)| Arbitrum | 42161 | 0xaf…831 |
-
low Secrets in code
secret-high-entropy-tokensrc/paywall.py:16High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"base": "0x83…913",
quoted -
low Secrets in code
secret-high-entropy-tokensrc/paywall.py:17High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"ethereum": "0xA0…B48",
quoted -
low Secrets in code
secret-high-entropy-tokensrc/paywall.py:18High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"polygon": "0x3c…359",
quoted -
low Secrets in code
secret-high-entropy-tokensrc/paywall.py:19High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"arbitrum": "0xaf…831",
quoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 151 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill
Process rating: all ten parameters 55/100
- 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
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (agent-economy) differs from the folder (x402-paywall)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 12 steps
- 100Execution cost. Instruction body is 1613 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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)
- +1No license
- +2Single-language instructions
- +3Description length 151: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 12 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: suspicious
This payment skill is mostly coherent, but it needs review because it can move real funds while its advertised payment verification is too weak to enforce the paywall safely.
LLM: suspicious (high) · VirusTotal: · 29 May 2026