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 Peiiii/nextclaw --skill gemigo-cligit clone --depth 1 https://github.com/Peiiii/nextclawWrote 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/peiiii/nextclaw/gemigo-cli)<a href="https://agentmods.dev/skills/peiiii/nextclaw/gemigo-cli"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/gemigo-cli/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/peiiii/nextclaw/gemigo-cli"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/gemigo-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 22 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 81 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 97 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00065 | $0.02772 |
| Opus 5.5 | $0.00026 | $0.01109 |
| Sonnet 5.5 | $0.00013 | $0.00554 |
| Haiku 4.5 | $0.00006 | $0.00277 |
Grade A, and why
gemigo-cli 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 1mo 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 — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GemiGo CLI
Overview
Use this skill when the user wants to publish an already-built static website or front-end app through the local gemigo CLI from inside NextClaw, then get a hosted public URL.
This skill is intentionally decoupled:
- The skill owns explanation, onboarding, readiness checks, workflow selection, risk disclosure, and success verification.
- The
gemigoCLI owns the actual login and deployment calls to GemiGo.
From the user's point of view, the experience should feel complete:
- install or verify the local CLI,
- confirm login state against the intended origin,
- validate that the target is a built static output directory,
- create or fix
gemigo.app.json, - ask for explicit confirmation before remote write actions,
- then deploy and report the resulting hosted URL.
Do not pretend the environment is ready when it is not.
What Users Can Deploy
Use plain language with the user: this skill helps them put a finished front-end app online.
Good fits:
- a Vite, React, Vue, Svelte, Astro, or similar front-end app after it has been built into
dist,build,out, or another static output directory - a plain HTML/CSS/JavaScript page or mini app
- a landing page, portfolio page, product demo, prototype, docs site, or static dashboard
- a small browser-only tool that does not need its own server process
- a zipped or generated static folder that contains
index.html
Not a fit unless the project is first converted to static output:
- a raw source repository root
- a Node/Express/Nest server app
- a Next.js app that still needs server-side rendering at runtime
- a backend API, database service, worker service, or long-running process
- anything that requires secrets or server code to run after deployment
If the user says "deploy my app" and gives you source code, first help them build it. Only deploy the generated static output folder.
Current Product Boundary
Current gemigo scope is intentionally narrow:
- generate a complete static-app manifest with
gemigo init - preflight the manifest and static output directory with
gemigo validate - log in with
gemigo login - inspect login state with
gemigo whoami - clear login state with
gemigo logout - publish a prebuilt static site directory with
gemigo deployorgemigo publish
What ships with it
1 file 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.
- 1mo ago First seen · 428 lines · 65 tokens per session scan A d4b3ebb580b1
gemigo-cli is a skill published in the GitHub repository Peiiii/nextclaw (262 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 2,772 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
openclaw-bun-upgrade
Qualify and promote a pinned Bun fork build for a Linux OpenClaw service, including upstream sync, release proof, native workload admission, and rollback planning.
add-vercel
Add Vercel deployment capability to NanoClaw agents. Installs the Vercel CLI in agent containers and sets up OneCLI credential injection for api.vercel.com. Use when the user wants agents to deploy web applications to Vercel.
ha-skill-creator
Create, edit, improve, or audit Hope Agent skills. Use when the user wants to: (1) create a new skill from scratch, (2) edit or improve an existing skill, (3) review or clean up a SKILL.md file, (4) run evaluations to test skill effectiveness, (5) optimize skill descriptions for better trigger accuracy. Trigger…
ha-browser
Hope Agent browser automation — the standard status → tabs → snapshot → act loop, stale-ref recovery rules, and what to do when login / 2FA / captcha / camera-prompt / dialog blocks progress. Load this skill whenever you reach for the browser tool. Trigger on: user asks the agent to open / control / click / scrape /…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
status-report
Use when the user asks for a weekly / monthly status report, project update, individual or team progress summary. Produces a tight, scannable update with what shipped, what's in flight, what's blocked, and metrics.