BB tpn-proxy
Make web requests through decentralized SOCKS5 proxies via the Tao Private Network (TPN). This skill is also known as "TPN", "TPN proxy", "subnet 65", or "SN65" — if the user asks to "run TPN", "use a proxy", "use TPN to open", or references "subnet 65", this is the skill they mean. Use when the user wants to route HTTP traffic through a proxy, make anonymous web requests, access geo-restricted content, use a decentralized VPN, fetch a URL through a SOCKS5 proxy, or needs residential proxy IPs. Supports both centralised API key authentication and decentralised x402 micropayments.
Make web requests through decentralized SOCKS5 proxies via the Tao Private Network (TPN).
As a process B 71/100 · Nearly there — weak spots: inputs and preconditions
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 contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
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 · 10
✓ No critical or high findings
Medium and low: 10
-
medium Concealment
en-hide-from-userSKILL.md:277Instruction to hide actions from the user (detector / deny-list definition)The pattern: **the user asks, you act, you return results.** You never tell the user how to call the API — you call it yourself and hand them the output.
detector -
low Exfiltration
net-credential-usereferences/api-examples.md:29Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl --proxy "socks5h://$USERNAME:$PASSWORD@$HOST:$PORT" \
fixture -
low Secrets in code
secret-high-entropy-tokenreferences/x402-examples.md:55High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)const USDC_ADDRESS = '0x83…913'
fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/x402-examples.md:135High-entropy token-like string (may be an id, hash or a credential) (documentation table row; test fixture / example file)| Contract | `0x83…913` |
tablefixture -
low Secrets in code
secret-high-entropy-tokenSKILL.md:168High-entropy token-like string (may be an id, hash or a credential)> Password: p_sT…Q7V
-
low Secrets in code
secret-password-literalSKILL.md:168Hard-coded password / key literal (may be an example)> Password: p_sT…Q7V
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:227High-entropy token-like string (may be an id, hash or a credential)> Password: p_CI…sQn
-
low Secrets in code
secret-password-literalSKILL.md:227Hard-coded password / key literal (may be an example)> Password: p_CI…sQn
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:323High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"password": "p_sT…Q7V",
quoted
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "aliases"
Process rating: all ten parameters 71/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4852 tokens
- 100Steps. 38 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 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)
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 586: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 38 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (2 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.