Wox: Skill for Codex

.agents/skills/wox-cpu-debug/SKILL.md

wox-cpu-debug is a skill for Codex from Wox-launcher/Wox. It costs 81 tokens per session (3,395 once invoked), scanned A, original, GPL-3.0.

A skill for finding where a Wox Go desktop interface uses CPU and measuring the cost of queries, plugins, rendering, native platform work, and background tasks.

In plain words
What is it for?
Use it to investigate CPU regressions, high idle or hidden CPU use, continuous-query costs, plugin and query hot paths, renderer activity, and work that continues in the background.
Why use it?
It helps identify the source of high or unnecessary CPU use while keeping the real single-process application's Go and native memory from growing materially.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is Wox-launcher/Wox's own configuration. It tells Codex how to work on Wox itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Wox configures →

About the project

Wox is a native desktop launcher for macOS, Linux, and Windows that combines app and file search with keyboard-driven actions in one input. People use it to open applications, find files, run actions, and extend the launcher with plugins. The catalogue includes ten skills and one instruction for Wox.

Wox-launcher/Wox · 27,323 stars · on GitHub · woxlauncher.com

Reuse

Borrowing it

Nothing to install: this file belongs to Wox-launcher/Wox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Wox-launcher/Wox/master/.agents/skills/wox-cpu-debug/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Wox-launcher/Wox

Made for: Codex.

Wrote 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.

agentmods badge for wox-cpu-debug

README.md
[![agentmods](https://agentmods.dev/badge/skills/wox-launcher/wox/wox-cpu-debug.svg)](https://agentmods.dev/skills/wox-launcher/wox/wox-cpu-debug)
Your own site
<a href="https://agentmods.dev/skills/wox-launcher/wox/wox-cpu-debug"><img src="https://agentmods.dev/badge/skills/wox-launcher/wox/wox-cpu-debug.svg" alt="Measured on agentmods" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,395 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00081 $0.03395
Opus 5 $0.00041 $0.01698
Sonnet 5 $0.00016 $0.00679
Haiku 4.5 $0.00008 $0.00340

Measured 7d ago against content hash b11506448ce6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

wox-cpu-debug 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/sample-wox-cpu-macos.sh, scripts/sample-wox-cpu-windows.ps1), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/wox-cpu-debug/SKILL.md · 238 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Files

What ships with it

4 files 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.

Changes

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.

  1. 7d ago First seen · 238 lines · 81 tokens per session scan A b11506448ce6

Subscribe to this mod's changes

wox-cpu-debug is a skill published in the GitHub repository Wox-launcher/Wox (27,323 stars, last pushed yesterday), licensed GPL-3.0. It adds 81 tokens to every session and 3,395 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens