SKILLEMALL.ai
GitHub ↗ RU Sign in

BB rug-checker

Solana token rug-pull risk analysis. 10-point on-chain check with visual report. Zero API keys. Read-only. Not financial advice.

modbender/skill-library-mcp Agent Skills author: modbender MIT 9 files · 4 scripts body ≈ 2 156 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Solana token rug-pull risk analysis.

As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice

AnalyzerDiscordAI and agentsData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
79/100
safety, quality, tests
Safety 60%
86
Quality 40%
68
Run on models
none yet
Process rating
B
65/100
Nearly there
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 14

✓ No critical or high findings

Medium and low: 14
  • low Secrets in code secret-high-entropy-token README.md:6
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    > "Rug check DezX…263"
    quoted
  • low Secrets in code secret-high-entropy-token README.md:50
    High-entropy token-like string (may be an id, hash or a credential)
    ║  Mint:   DezX…263
  • low Secrets in code secret-high-entropy-token README.md:110
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    - *"Rug check DezX…263"*
    quoted
  • low Secrets in code secret-high-entropy-token README.md:120
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    bash scripts/detect-token.sh DezX…263
    detector
  • low Secrets in code secret-high-entropy-token README.md:123
    High-entropy token-like string (may be an id, hash or a credential)
    bash scripts/analyze-risk.sh DezX…263
  • low Secrets in code secret-high-entropy-token scripts/detect-token.sh:26
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    detect-token.sh DezX…263
    detector
  • low Secrets in code secret-high-entropy-token SKILL.md:40
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Token lookup + Solana address | "What is DezX…263?" |
    table
  • low Secrets in code secret-high-entropy-token SKILL.md:201
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "Rug check DezX…263"
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:203
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "Check this token for me: 5smi…ump"
    quoted
  • low Secrets in code secret-high-entropy-token TESTING.md:18
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row; test fixture / example file)
    | BONK | `DezX…263` | Blue chip meme | 🟢 SAFE |
    tablefixture
  • low Secrets in code secret-high-entropy-token TESTING.md:19
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; documentation table row; test fixture / example file)
    | USDC | `EPjF…t1v` | Stablecoin | 🟠 WARNING (has compliance authorities) |
    detectortablefixture
  • low Secrets in code secret-high-entropy-token TESTING.md:27
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; test fixture / example file)
    bash scripts/detect-token.sh DezX…263
    detectorfixture
  • low Secrets in code secret-high-entropy-token TESTING.md:61
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
    bash scripts/analyze-risk.sh DezX…263 2>/dev/null | jq '{tier, score: .composite_score, checks_count: (.checks | length)}'
    fixture
  • low Secrets in code secret-high-entropy-token TESTING.md:83
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
    bash scripts/analyze-risk.sh EPjF…t1v 2>/dev/null | jq '{tier, score: .composite_score, name: .token.name, symbol: .token.symbol}'
    fixture

Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "permissions"

Process rating: all ten parameters 65/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 100Steps. 26 steps
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 4 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2156 tokens
  • 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

  • +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 4 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 128: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 26 items
  • +4Has examples (6 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.