Cost Governor
v1.0.1Tracks LLM API costs in real-time, enforces budget limits with circuit breakers, and enables autonomous agent payments via the x402 protocol.
⭐ 0· 1.1k·5 current·5 all-time
by@atlaspa
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
SKILL.md and README describe autonomous cost tracking + agent-initiated payments via x402 (requiring a funded wallet). The skill declares only 'node' as a required binary and no environment variables or credentials — but autonomous payments logically require wallet credentials or a payment integration. The absence of any declared credential or config explanation is inconsistent with the described payment capability.
Instruction Scope
Runtime instructions tell the operator to run 'npm install' and 'npm run setup', run 'node src/cli.js' commands, register OpenClaw hooks, and expose a local web API for x402 payments. However, the published skill contains no code files (no src/cli.js or package.json). The instructions also tell operators to 'Give agent access to funded wallet', which expands scope to sensitive wallet access without specifying how that access is granted or constrained.
Install Mechanism
The skill is instruction-only and provides no install spec, yet the instructions expect an npm-based install (and reference project files). This mismatch is risky: following the instructions would cause you to run npm install (source unspecified) which could fetch arbitrary packages. Because no package origin or install manifest is included in the skill bundle, it is unclear what code will be installed or from where.
Credentials
Declared requirements list no env vars or credentials, but the documentation repeatedly instructs giving agents access to a funded wallet and calling local payment endpoints. That implies access to sensitive secrets (private keys or wallet signing capability) that are not declared or scoped. This is disproportionate and under-specified.
Persistence & Privilege
always:false (good) but the skill is allowed autonomous invocation (platform default). Combined with the skill's claim to allow agents to autonomously pay real funds, this raises significant risk: an autonomously-invokable skill that can cause financial transactions should explicitly declare and constrain how wallets/keys are used. The skill provides no such constraints or safeguards (MVP trusts reported tx hashes), increasing potential for unintended payments.
What to consider before installing
Do not run the npm commands or hand over wallet credentials until these questions are answered and you can review code: 1) Where is the package source? Require a concrete repository or npm package name and a verifiable checksum before running npm install. 2) Provide the package files (package.json, src/cli.js) in the skill bundle so the skill's runtime behavior can be audited. 3) Explain exactly how autonomous payments are performed: does the skill need a private key, a signing service, or a hardware wallet? Never give private keys or unfettered wallet access to an agent. 4) Prefer on-chain verification (production) and require signed transactions from a hardware wallet / human approval for payments > a minimal test amount. 5) If you must test, run in an isolated environment with a funded test wallet and no real funds, and inspect network activity and installed package contents first. Given the inconsistencies (no code shipped, but instructions to install/run code and to grant wallet access), treat this skill as untrusted until the developer provides verifiable source and clear credential handling.Like a lobster shell, security has layers — review code before you run it.
latestvk97afv5g3t3ehtrnvms6ch6591811q9h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
💰 Clawdis
OSmacOS · Linux · Windows
Binsnode