CC litcoin-miner
Mine LITCOIN — a proof-of-comprehension and proof-of-research cryptocurrency on Base. AI agents earn tokens by solving reading comprehension challenges and real optimization problems. Full DeFi: staking, vaults, LITCREDIT stablecoin, guilds, compute marketplace, autonomous agents.
As a process C 59/100 · Has gaps — weak spots: result and completion, 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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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.
- 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 · 10
✓ No critical or high findings
Medium and low: 10
-
medium Exfiltration
net-credential-useSKILL.md:73Credential used in a network call (verify the destination is the intended service)curl -s https://api.bankr.bot/agent/me -H "X-API-Key: $BANKR_API_KEY"
-
low Secrets in code
secret-high-entropy-tokenreferences/protocol.md:174High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Faucet contract: `0x16…557`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/protocol.md:199High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Guild contract: `0xC3…bD1`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/protocol.md:222High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)LITCREDIT token: `0x33…0a6`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/protocol.md:239High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)VaultManager contract: `0xD2…058`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/protocol.md:361High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| LITCOIN (ERC-20) | `0x31…Ba3` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:112High-entropy token-like string (may be an id, hash or a credential)# LITCOIN token: 0x31…Ba3
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:116High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)-d '{"prompt": "swap $10 of ETH to 0x31…Ba3 on base"}'quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:475High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Buying LITCOIN: `"swap $10 of ETH to 0x31…Ba3 on base"`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:584High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Token**: `0x31…Ba3` (100B supply, 18 decimals)
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 281 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 - warning
body-longSKILL.md body ≈ 5665 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 8 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, python, node) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5665 tokens
- 85Steps. 71 steps, 1 vague phrases
- 100Failures and branches. 4 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +3Description length 281: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 71 items
- +4Has examples (23 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 52.