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 publish-to-nextclaw-marketplacegit 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/publish-to-nextclaw-marketplace)<a href="https://agentmods.dev/skills/peiiii/nextclaw/publish-to-nextclaw-marketplace"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/publish-to-nextclaw-marketplace/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/publish-to-nextclaw-marketplace"><img src="https://agentmods.dev/badge/skills/peiiii/nextclaw/publish-to-nextclaw-marketplace.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.00053 | $0.01579 |
| Opus 5 | $0.00026 | $0.00790 |
| Sonnet 5 | $0.00011 | $0.00316 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade C, and why
publish-to-nextclaw-marketplace scanned grade C with 2 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 9d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$tmp_dir" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS https://marketplace-api.nextclaw.io/api/v1/skills/items/%40alice%2Fmy-skill How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish To NextClaw Marketplace
Overview
Use this skill when the user wants to publish a local skill to the NextClaw marketplace or update an existing listing.
This skill owns the full publishing loop:
- check that the local
nextclawversion is new enough, - verify platform identity and username readiness,
- choose the correct package scope,
- run
publishorupdate, - then verify the listing and install path.
Do not pretend the account is ready when it is not. If the user is logged in but still has no platform username, stop and ask them to set it first.
Hard Requirement
This workflow requires NextClaw v0.17.6 or later.
Why:
v0.17.6+is the baseline that supports scoped marketplace package names such as@nextclaw/my-skilland@alice/my-skill.- It also supports the clearer
--scopeand--package-namepublish parameters. - Personal publishing now depends on the platform
usernamemodel added in the same release line.
Always verify first:
nextclaw --version
If the version is lower than 0.17.6, do not continue with a fallback flow.
Tell the user to upgrade NextClaw first.
Marketplace Identity Model
Treat these fields differently:
slug: the local skill directory name and the skill name segmentpackage name: the canonical marketplace identifier, shaped like@scope/skill-name
Publishing scopes:
- official scope:
@nextclaw/<skill-name> - personal scope:
@<username>/<skill-name>
Rules:
@nextclaw/*publishing requires admin permission orNEXTCLAW_MARKETPLACE_ADMIN_TOKEN- personal publishing requires an active platform login
- personal publishing also requires a platform username
- the personal scope must exactly match the current username
Do not blur official and personal publishing together.
Readiness Checklist
Before publishing, check these in order.
1. CLI version
nextclaw --version
Must be 0.17.6 or later.
2. Platform login
For normal user publishing, log in first:
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.
- 9d ago First seen · 242 lines · 53 tokens per session scan C b3a43535d7b1
publish-to-nextclaw-marketplace is a skill published in the GitHub repository Peiiii/nextclaw (256 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,579 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). 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-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.
openclaw-pr-batch-sweep
Select, review, repair, validate, and land batches of up to 20 low-risk OpenClaw contributor pull requests using Vincent's maintainer preferences and bounded sub-agent lanes. Use for "next 20", broad contributor PR sweeps, merge-candidate mining, or continued PR-batch work where drafts, maintainer work, trivial…
tmux-lane-orchestrator
Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.
ghcrawl-cluster-operator
Use when inspecting a ghcrawl SQLite store, pulling GitHub issue/PR data, refreshing summaries, embeddings, and clusters, or extracting one cluster and its evidence through the ghcrawl CLI.
opik-optimizer
Optimize LLM prompts, tools, and agents in Opik using standardized optimizer workflows (prompt optimization, tool optimization, and parameter tuning), dataset/metric wiring, and result interpretation.
org-branch-cleanup
Audit and safely prune stale branches across a GitHub organization with immutable snapshots, conservative merged-PR classification, live SHA/protection/open-PR revalidation, resumable deletion ledgers, and post-delete verification. Use when a maintainer asks to clean up old, dead, merged, bot-created, or abandoned…