BC hypha-payment
P2P agent coordination and USDT settlement via the Hypha Network. Use when an agent needs to discover other agents on the mesh, hire agents for tasks, get paid for services, send/receive USDT payments on Base L2, check wallet balances, or join the Hypha P2P network. Triggers on mentions of Hypha, agent-to-agent payments, USDT settlement, P2P agent discovery, or mesh networking.
P2P agent coordination and USDT settlement via the Hypha Network.
As a process C 57/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice
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
- 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
-
medium Risky intent
intent-wallet-secretsSKILL.md:124Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- `PRIVATE_KEY` — Override wallet private key (instead of seed derivation)
-
low Secrets in code
secret-high-entropy-tokenreferences/network.md:13High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Escrow**: `0x7b…E6F`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/network.md:14High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDT**: `0x03…F7e`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/network.md:21High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Foundation Wallet**: `0x5C…A2E`
quoted -
low Risky intent
intent-wallet-secretsscripts/setup_agent.py:32Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)print(f" Seed Phrase: {seed_phrase}")quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 832 tokens
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)
- +3Output format is not stated: the model decides each time
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 380: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.