SKILLEMALL.ai

BF Cost Control 3-Tier API Spend Protection

Prevent runaway API costs with 3-tier protection: caution, emergency, and hard cap. Works for ANY expensive API GPT-4, Claude Opus, Gemini, cloud services.

ClawHub Agent Skills author: Shadow Rose v1.0.3 MIT-0 9 files body ≈ 4 142 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 41/100 · Will not run — References files that are not bundled: LICENSE

IntegrationDiscordGitHubInfrastructureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
98
Quality 40%
60
Run on models
none yet
Process rating
F
41/100
Will not run
References files that are not bundled: LICENSE
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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.
  2. The text references files that are not there: add them or drop the references.
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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Dangerous commands cmd-cron-mention README.md:315
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention SKILL.md:329
    Mentions editing / listing crontab
    crontab -e

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: LICENSE

Process rating: all ten parameters 41/100

Will not run. References files that are not bundled: LICENSE
  • 0Tools and files. 1 referenced file(s) missing: LICENSE
  • 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
  • 40Consistency. Frontmatter name (Cost Control 3-Tier API Spend Protection) differs from the folder (cost-control)
  • 70Execution cost. Instruction body is 4142 tokens
  • 100Steps. 95 steps
  • 100Failures and branches. 3 branches, has a failure section
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 25 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
  • -217 emoji in the instructions: noise for the model
  • +2Single-language instructions
  • +3Description length 155: enough signal without eating the budget
  • +4Structure: 71 headings
  • +3Step-by-step instructions: 95 items
  • +4Has examples (19 code blocks)
  • +1License stated

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

External checks

ClawHub: clean
This is a disclosed API cost-control skill; its kill-switch behavior is high impact but aligned with its stated purpose and user-enabled setup.
LLM: benign (high) · VirusTotal: · 29 May 2026