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 QwenCloud/qwencloud-ai --skill qwencloud-usagegit clone --depth 1 https://github.com/QwenCloud/qwencloud-aiWrote 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/qwencloud/qwencloud-ai/qwencloud-usage)<a href="https://agentmods.dev/skills/qwencloud/qwencloud-ai/qwencloud-usage"><img src="https://agentmods.dev/badge/skills/qwencloud/qwencloud-ai/qwencloud-usage.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.1 | $0.00057 | $0.03168 |
| Opus 5 | $0.00028 | $0.01584 |
| Sonnet 5 | $0.00011 | $0.00634 |
| Haiku 4.5 | $0.00006 | $0.00317 |
Grade A, and why
qwencloud-usage 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 7d 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QwenCloud Usage
Query QwenCloud usage, free tier quota, coding plan status, and pay-as-you-go billing.
Prerequisites
- QwenCloud CLI must be installed. Verify with:
qwencloud version
If not installed, run:
npm install -g @qwencloud/qwencloud-cli
Node.js >= 18 required.
- Authentication: No configuration needed on first use. The CLI handles non-TTY detection and safe login automatically (see Authentication Flow below).
Environment Variables
| Variable | Description |
|---|---|
QWENCLOUD_KEYRING |
Set to plaintext, no, 0, false, or off to opt out of OS keychain credential storage. |
QWENCLOUD_CREDENTIALS_DIR |
Override file-based credential directory (default: ~/.qwencloud/credentials). |
Authentication Flow (for Agents)
The CLI auto-detects non-TTY environments and degrades safely — no wrapper script needed.
TL;DR — 3-step auth path
qwencloud auth status --format json→authenticated: true→ skip to commandsqwencloud auth login --init-only --format json→ extractverification_url→ open in browserqwencloud auth login --complete --format json→ poll untilsuccessevent
Quick check: already logged in?
qwencloud auth status --format json
If authenticated: true and token is not expired, skip login entirely.
Recommended: Two-phase login
Works in all environments (desktop, headless, remote container).
Step 1 — Initialize login (non-blocking):
qwencloud auth login --init-only --format json
Exits immediately. Parse the stdout JSON events array:
already_authenticated→ user is logged in, skip to commandsdevice_code→ extractverification_urland present it to the user
On desktop environments with a browser, open the URL for the user:
open "$VERIFICATION_URL" # macOS
xdg-open "$VERIFICATION_URL" # Linux
start "" "$VERIFICATION_URL" # Windows
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.
- 7d ago First seen · 348 lines · 57 tokens per session scan A 0ed5ecab9f6b
qwencloud-usage is a skill published in the GitHub repository QwenCloud/qwencloud-ai (39 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 3,168 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
sector-rotation
An analysis framework for comparing industries in the Chinese A-share stock market, using business conditions, price momentum, valuation, and money flows. It produces rankings and higher- or lower-allocation suggestions.
strategy-pivot-designer
Detect backtest iteration stagnation and generate structurally different strategy pivot proposals when parameter tuning reaches a local optimum.
twitter-reader
Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…
chenhao-limit-up
A framework for judging Chinese A-share stocks that have reached the daily price-rise limit, using market mood, sector leadership, and trading momentum.
trading-risk-gate
Unified pre-trade safety gate: Ruin check (Law #1), ergodicity audit, and win-rate dominance validation. Absorbs: ergodicity-check, law-of-ruin, win-rate-dominance.
vectorbt
High-performance vectorized backtesting with parameter optimization, portfolio simulation, and rich performance metrics.