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/davidomil/cloudx/ship-changenpx skills add davidomil/cloudx --skill ship-changegit clone --depth 1 https://github.com/davidomil/cloudxWhat 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.00022 | $0.00456 |
| Opus 5 | $0.00011 | $0.00228 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
ship-change 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 yesterday.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Change
Responsibility
This is the sole skill allowed to mutate GitHub for the AI change process. It may push an already prepared branch, open or update a PR, reconcile labels, submit an authorized review, and request a merge only when policy permits. It does not plan, implement, verify, or review code.
Preconditions
- Valid current plan, implementation, verification and clean review artifacts.
- Clean
$review-prartifact for the live PR head. - Current policy classification and reconciled label set.
- A
.agents/schemas/merge-intent.schema.jsonartifact for the same PR head. - Explicit user authorization for the requested GitHub mutation.
Before a merge action, reread the live pull request and prove that required checks, clean review, resolved conversations, protected-path approval, merge intent, and head SHA are all current. Automated merge authority belongs to the private controller; this public skill must not substitute a local merge path.
Procedure
- Re-read the live PR head immediately before mutation.
- Refuse stale artifacts, missing checks, neutral/skipped/cancelled checks, unresolved conversations or a different head.
- Reconcile managed labels; remove stale managed labels as well as adding current ones.
- For
human-requiredorautomerge: falseclassifications, prepare the PR handoff and stop before automatic merge. - For an eligible authorized change, request the policy-approved squash merge
path and verify the live result. Do not claim
mergedfrom an enqueue acknowledgement. - Record the exact command/API operation and authoritative readback.
Output
Report PR URL/number, branch, exact head, labels changed, review/merge operation,
readback state and remaining action. Only record the state-machine merged
transition after the authorized exact head is confirmed on the base branch.
Prohibitions
No force push, no direct protected-branch push, no merge-policy bypass, no blind
retry, and no mutation based only on trusted-auto-merge.
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.
- yesterday First seen · 52 lines · 22 tokens per session scan A 790bbd3ef185
ship-change is a skill published in the GitHub repository davidomil/cloudx (1 stars, last pushed 9d ago), licensed MIT. It adds 22 tokens to every session and 456 once invoked, about $0.0001 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-31.
Other skills, from other repositories
verify-pr
This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr ", "深度验证这个 PR", A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates — producing tmp/pr -verify- /report.md plus a machine-readable verdict. Designed for the token-free CI…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop-shell.
coordinate
Coordinate a small team of Qwen Code teammates with enforced read-only workers, an optional worktree-pinned writer, shared tasks, peer messages, and existing Agent View tabs. Invoke explicitly with /coordinate.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…