Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add javimosch/supercli --skill setupgit clone --depth 1 https://github.com/javimosch/supercliWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/javimosch/supercli/setup)<a href="https://agentmods.dev/skills/javimosch/supercli/setup"><img src="https://agentmods.dev/badge/skills/javimosch/supercli/setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/javimosch/supercli/setup"><img src="https://agentmods.dev/badge/skills/javimosch/supercli/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.00402 |
| Opus 5.5 | $0.00008 | $0.00161 |
| Sonnet 5.5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
clawteam.system.setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
ClawTeam System Setup
Use this workflow if you encounter a "missing dependency" error when trying to use ClawTeam commands.
Commands
clawteam <resource> <action>— Execute clawteam commandsclawteam system setup— Automated installation of ClawTeam platform (Gateway, API, DB, Redis). Suitable for AI agents.clawteam system start— Start all ClawTeam services (Docker + Gateway)clawteam system stop— Stop all ClawTeam servicesclawteam system status— Check full health of ClawTeam platform (Docker + Gateway)clawteam gateway status— Show local ClawTeam gateway process statusclawteam agents list— List shared agents and active sessions in the networkclawteam task delegate— Delegate a task to an expert agent in the ClawTeam network
1) Detect Missing Dependency
If a command fails with:
"Missing dependency 'clawteam-gateway'. Please install ClawTeam Gateway..."
You should proceed to automated setup.
2) Run Automated Setup
Execute the following command to clone the repository, install dependencies, and create the necessary binary shims:
supercli clawteam system setup --json
3) Verify Installation
Check if the gateway binary is now accessible and the system is healthy:
# Verify binary
clawteam-gateway --version
# Check full system status (including Docker services)
supercli clawteam system status --json
4) Start Services
If everything is installed but services are not running:
supercli clawteam system start --json
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 55 lines · 21 tokens per session scan A d8251921378c
clawteam.system.setup is a skill published in the GitHub repository javimosch/supercli (56 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 402 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-29.
Other skills, from other repositories
wrangler
Run or troubleshoot Wrangler CLI commands in projects that have a wrangler.jsonc, wrangler.json, or wrangler.toml file, including local development, Previews, deployment, and resource management. For new projects and projects without a Wrangler configuration file, use the cf CLI instead.
managing-astro-local-env
Manage local Airflow environment with Astro CLI (Docker and standalone modes). Use when the user wants to start, stop, or restart Airflow, view logs, query the Airflow API, troubleshoot, or fix environment issues. For project setup, see setting-up-astro-project.
bailian-sandbox
A command-line interface for creating, inspecting, connecting to, pausing, resuming, and deleting Alibaba Cloud Bailian sandbox environments. A sandbox is an isolated workspace for running tools or code.
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations. Not for: a loom orchestration job or CI pipeline job — see loom-ci-cd.
loom-kustomize
Kubernetes-native configuration management with Kustomize.
loom-docker
Docker and container expertise.