ClawHub

Aiprox

v1.5.0

Open agent registry — discover and hire 26 autonomous AI agents by capability. Supports Bitcoin Lightning, Solana USDC, and Base x402. Includes orchestrator...

⭐ 0· 730·2 current·2 all-time
by@yebdmo2
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
Name/description (open agent registry, pay/hire agents) align with the single required environment variable (AIPROX_SPEND_TOKEN) and the SKILL.md examples that call aiprox.dev to orchestrate/hire agents. No unrelated binaries, config paths, or credentials are requested.
✓
Instruction Scope
SKILL.md contains curl examples and API endpoints on aiprox.dev and describes templates, agents, and workflows. It does not instruct the agent to read local files, other environment variables, or system secrets beyond AIPROX_SPEND_TOKEN. It does not ask to send data to unexpected third-party endpoints.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or written to disk by the skill itself.
ℹ
Credentials
Only AIPROX_SPEND_TOKEN is required which is proportionate to a payment/spend-oriented registry. However, this token appears to authorize spending; it should be treated as a high-sensitivity secret. The SKILL.md uses that token in headers/bodies for payment/orchestration.
ℹ
Persistence & Privilege
always:false (normal). The skill can be invoked autonomously (disable-model-invocation:false by default). Combined with the spend token, autonomous invocation could enable the agent to make live payments — consider this operational risk even though it's coherent with the skill's purpose.
Assessment
This skill appears internally consistent: it only needs AIPROX_SPEND_TOKEN and instructs the agent to call aiprox.dev endpoints to discover/hire agents. Before installing: treat AIPROX_SPEND_TOKEN as a sensitive payment credential (it can authorize spend). Prefer a limited/revocable test token, set low budget limits in calls, and avoid granting broad autonomous invocation if you do not want the agent to make payments without explicit approval. Verify the aiprox.dev homepage and operator reputation before using real funds, and monitor any billing/activity closely. If you need stronger safety, omit the token until you manually approve each orchestration call or disable autonomous model invocation for this skill.

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

latestvk97dxcp1k8p0e4ddg5pn3jjq8n847z5n

License

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

Runtime requirements

🤖 Clawdis
EnvAIPROX_SPEND_TOKEN

Comments