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/plan-changenpx skills add davidomil/cloudx --skill plan-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.00019 | $0.00332 |
| Opus 5 | $0.00010 | $0.00166 |
| Sonnet 5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
plan-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.
What it actually says
Plan Change
Responsibility
Design the change at the correct owner and define proof before code is written. Do not edit code, review the plan, or mutate GitHub.
Inputs
- Original task, base/head SHA, and policy digest.
- Classification from
.agents/pr-review-policy.toml. - Root and all applicable scoped
AGENTS.mdfiles. - Policy-selected area skills and current source/tests.
Run in a fresh context. Research the current code and read every proposed file. Trace at least two analogous repository implementations.
Required Plan
Produce JSON that validates against .agents/schemas/plan.schema.json with:
- exact task, SHAs, policy digest, and selected skill digests;
- type, areas, risk, skills, human-review requirement and automerge eligibility;
- at least two path/line anchors and why each is analogous;
- behavioral claims with owner/seam, production-path test, and negative cases;
- explicit allowed and forbidden paths;
- exact verification commands from
docs/architecture/testing-map.md.
Place behavior at the owner in docs/architecture/module-ownership.md. Account
for every affected invariant in docs/architecture/state-invariants.md. If the
task requires a compatibility layer, record the break and stop for explicit user
approval before planning compatibility.
Stop Conditions
Return a blocking gap instead of guessing when ownership, behavior, external requirements, or a safe proof strategy is unresolved. Scope outside allowed paths requires a new complete plan.
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 · 44 lines · 19 tokens per session scan A c773f8993495
plan-change is a skill published in the GitHub repository davidomil/cloudx (1 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 332 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…