ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

SatGate

v0.1.2

Manage your API's economic firewall from the terminal. Mint tokens, track spend, revoke agents, enforce budgets. The server-side counterpart to lnget.

⭐ 0· 779·1 current·1 all-time
by@matt-dean-git
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
ℹ
Purpose & Capability
Name/description, SKILL.md, and included scripts all describe a CLI that mints/revokes tokens and talks to a SatGate gateway — that aligns. However, the registry metadata declares no required environment variables or primary credential while the README and configure.sh clearly expect admin/session tokens and several SATGATE_* env vars. The omission reduces transparency and makes automated platform checks impossible.
✓
Instruction Scope
SKILL.md and the scripts keep to the stated domain: installing the satgate binary, configuring ~/.satgate/config.yaml, and calling the gateway (satgate ping/status). There are no instructions to read unrelated system files or exfiltrate data. The SKILL.md suggests installing an unrelated plugin (lnget) for client-side payments, but that is a documented integration, not hidden behavior.
ℹ
Install Mechanism
install.sh downloads a prebuilt binary from GitHub releases (https://github.com/SatGate-io/satgate-cli), which is a standard release host — good. The script attempts to verify SHA256SUMS but explicitly skips verification if checksums are missing or system tools are absent; in that case the binary is installed without a verified checksum. The installer may use sudo to write to /usr/local/bin. These are reasonable choices but carry the usual risks of installing network-downloaded binaries without enforced verification.
!
Credentials
The skill manifest lists no required env vars or primary credential, yet SKILL.md and configure.sh expect and store sensitive values (admin_token, session_token, bearer_token, tenant) in ~/.satgate/config.yaml or via SATGATE_* env vars. Requiring admin/session tokens is reasonable for a gateway management CLI, but the manifest's omission is a transparency problem: the platform won't warn users or gate secret provisioning, and automated checks can't reason about needed privileges.
✓
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and only writes its own user-scoped config (~/.satgate/config.yaml) and can place a binary in standard locations (/usr/local/bin). These behaviors are typical for a CLI installer; expected privileges (filesystem write for installation, network access to the gateway) are within scope.
What to consider before installing
This skill appears to be what it claims — a CLI to manage SatGate gateways — but there are a few practical risks and transparency issues to consider before installing: - Verify the origin: the installer pulls a binary from GitHub (SatGate-io/satgate-cli). Visit that repository and confirm the release artifacts and SHA256SUMS match what you expect before running install.sh. - Prefer verified installs: if checksums are missing or your system lacks sha256 tools, the installer will skip verification. Consider building from source or obtaining the checksum directly from the official repo before installing. - Protect secrets: the CLI expects sensitive tokens (admin_token/session_token/bearer_token). configure.sh writes them to ~/.satgate/config.yaml with permissions 600, which is good, but only run this on machines you trust. The registry metadata should have declared those env vars — ask the publisher to update the manifest so the platform can surface required credentials to you. - Least privilege: create and use a scoped admin/session token with minimal privileges where possible rather than a full root credential. - Run health-check first: use scripts/health-check.sh to validate the binary and connection before performing destructive operations; use --dry-run and avoid --yes flags without human approval. If you need higher assurance, inspect the project's GitHub release binary and source code (or build from source) and confirm the vendor (satgate.io) and the GitHub org match officially published channels.

Like a lobster shell, security has layers — review code before you run it.

latestvk972xhpek2nt79xj2ydccbzqqd8118bz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments