nexu is an open-source desktop client that connects an OpenClaw AI agent to messaging services such as WeChat, Feishu, Slack, and Discord. It is for people who want to chat with their agent from those channels using their own model credentials while keeping data on their computer, and the catalogue entries support its agent workflows.
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 agentmods add skills/nexu-io/nexu/static-deploynpx skills add nexu-io/nexu --skill static-deploygit clone --depth 1 https://github.com/nexu-io/nexuWrote 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/nexu-io/nexu/static-deploy)<a href="https://agentmods.dev/skills/nexu-io/nexu/static-deploy"><img src="https://agentmods.dev/badge/skills/nexu-io/nexu/static-deploy.svg" alt="Measured on agentmods" 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 | $0.00060 | $0.01011 |
| Opus 5 | $0.00030 | $0.00505 |
| Sonnet 5 | $0.00012 | $0.00202 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
static-deploy 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 5d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Static Deploy
Deploy static files to <project-slug>.nexu.space via Wrangler + Cloudflare Pages.
The deploy script stages a temporary copy of the site and injects a _headers
file (if needed) with cache revalidation rules for HTML/CSS/JS to reduce stale
asset issues after redeploys. Source files are not modified.
What it deploys
Any static files: HTML, CSS, JS, images, fonts, etc. Common use cases:
- Single-page apps (React, Vue, etc. — deploy the
dist/orbuild/folder) - Landing pages, portfolios, documentation sites
- Quick prototypes or demos
- Any folder with an
index.html
Usage
- Identify the directory containing files to deploy (must have an
index.html) - Derive a project-slug from context (e.g., "family budget" →
family-budget)- Lowercase alphanumeric + hyphens only, max 63 characters
- Reuse the same slug for redeployments
- Ask user to confirm if ambiguous
- Run deploy with the inbound structured context:
"$SKILL_DIR/scripts/deploy.sh" <project-slug> <directory> <agent-id> <chat-id> [thread-id] [message-ref] [account-id] [channel] [chat-type] [sender-ref]
agent-id is required. The script uses it to resolve the corresponding botId
from nexu-context.json when recording deployment artifacts.
chat-id is the raw inbound chat identifier from the message context.
- DM example:
U0AHLMC6C8G - Channel example:
C0AJKG60H6D
chat-type tells the script whether to send that id to Nexu as user:<chat-id>
or channel:<chat-id>. The script does that translation; do not concatenate
those prefixes yourself.
thread-id is optional — pass it when deploying from within a thread context.
4. Parse the JSON output and report to user:
- Brief summary of what was deployed
- Live URL from the
urlfield - Important: Tell the user that Cloudflare Pages propagation takes ~3 minutes. The URL may not work immediately after the first deploy. For redeployments, it's usually faster.
Example reply
Deployed! Your site is live at https://family-budget.nexu.space
Note: First-time deploys take ~3 minutes to propagate on Cloudflare. If you see a "not found" page, wait a few minutes and refresh.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 96 lines · 60 tokens per session scan A 96cb2fa281de
static-deploy is a skill published in the GitHub repository nexu-io/nexu (3,262 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 1,011 once invoked, about $0.0003 per session on Opus 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-08-30.
Other skills, from other repositories
azure
Microsoft Azure expert for az CLI, AKS, App Service, and cloud infrastructure.
gcp
Google Cloud Platform expert for gcloud CLI, GKE, Cloud Run, and managed services.
aws
AWS cloud services expert for EC2, S3, Lambda, IAM, and AWS CLI.
kubernetes
Kubernetes operations expert for kubectl, pods, deployments, and debugging.
terraform
Terraform IaC expert for providers, modules, state management, and planning.
eng-runbook
An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief mentions "runbook", "ops doc", "on-call guide", "SRE doc", or "运维手册".