BC nexusweb3-safety
Read-only API reference for NexusWeb3 safety protocols 21-30 on Base mainnet — kill switch status, KYA verification, audit logs, bounties, licensing, milestones, subscriptions, insolvency, referrals, and collectives.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenREADME.md:11High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| 21 | AgentKillSwitch | `0xaf…E96` | Emergency stop with spending limits |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:18High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)- **USDC:** `0x83…913` (6 decimals)
detector -
low Secrets in code
secret-high-entropy-tokenSKILL.md:37High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)**Contract:** `0xaf…E96`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:472High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| AgentKillSwitch | `0xaf…E96` | 0.01 ETH registration |
table
Files scanned: 3. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 12 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Execution cost. Instruction body is 4955 tokens
- 100Steps. 12 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 216: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (31 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: clean
This is a documentation-only blockchain reference with risky transaction examples, but it contains no executable code, credentials, persistence, or automatic wallet access.
LLM: benign (high) · VirusTotal: · 29 May 2026