BC stipend
A non-custodial USDC wallet on Base that an AI agent installs by itself, with spending limits enforced in the signing path rather than in a prompt. Receive payments, pay HTTP 402 / x402 charges automatically, and answer whether you are worth running. No account, no API key, no human needed to install or to be paid.
A non-custodial USDC wallet on Base that an AI agent installs by itself, with spending limits enforced in the signing path rather than in a prompt.
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost
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.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
-
medium Dangerous commands
cmd-pipe-to-shellSKILL.md:37Downloads and executes remote code from an unrecognised host (pipe to shell) (the skill's own vendor host)curl -sL https://stipend.sh/install | sh
vendor-host -
medium Dangerous commands
cmd-pipe-to-shellSKILL.md:95Downloads and executes remote code from an unrecognised host (pipe to shell) (the skill's own vendor host)curl -sL https://stipend.sh/install | sh
vendor-host -
medium Dangerous commands
cmd-pipe-to-shellSKILL.md:251Downloads and executes remote code from an unrecognised host (pipe to shell) (the skill's own vendor host)> curl -sL https://stipend.sh/install | sh
vendor-host -
low Dangerous commands
cmd-pipe-to-shellSKILL.md:107Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation table row; the skill's own vendor host)| Shell, and it runs where your files are | `curl -sL https://stipend.sh/install \| sh` |
tablevendor-host
Files scanned: 2. 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") - warning
body-longSKILL.md body ≈ 9485 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Execution cost. Instruction body is 9485 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 100Steps. 29 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- +2Single-language instructions
- +3Description length 316: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (29 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.