qwen-omni-mcp: Skill for Claude Code

.agents/skills/health/SKILL.md

health is a skill for Claude Code, Codex from sommio/qwen-omni-mcp. It costs 71 tokens per session (3,882 once invoked), scanned A, original, MIT.

An engineering health audit for an AI-assisted coding project. It checks agent instructions and configuration, connected tools, automated checks, and how well the project can be maintained by people and coding agents.

In plain words
What is it for?
Use it to audit Codex, Claude, or Pi instructions, hooks, MCP servers, skills, verifier coverage, generated artifacts, and maintainability. It produces findings with evidence and suggested next actions.
Why use it?
It helps uncover configuration drift, missing verification, risky hooks or MCP connections, and other weaknesses in the project's agent setup.

Skill for Claude CodeCodex

Written for Claude Code and Codex: when-to-use in frontmatter, but also reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is sommio/qwen-omni-mcp's own configuration. It tells Claude Code and Codex how to work on qwen-omni-mcp 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 qwen-omni-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sommio/qwen-omni-mcp. 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/sommio/qwen-omni-mcp/develop/.agents/skills/health/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/sommio/qwen-omni-mcp

Made for: Claude Code, 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 health

README.md
[![agentmods](https://agentmods.dev/badge/skills/sommio/qwen-omni-mcp/health/github.svg)](https://agentmods.dev/skills/sommio/qwen-omni-mcp/health)
Your own site
<a href="https://agentmods.dev/skills/sommio/qwen-omni-mcp/health"><img src="https://agentmods.dev/badge/skills/sommio/qwen-omni-mcp/health/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.

agentmods 80×15 button for health

Your own site · 80×15
<a href="https://agentmods.dev/skills/sommio/qwen-omni-mcp/health"><img src="https://agentmods.dev/badge/skills/sommio/qwen-omni-mcp/health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,882 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 original 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.00071 $0.03882
Opus 5 $0.00036 $0.01941
Sonnet 5 $0.00014 $0.00776
Haiku 4.5 $0.00007 $0.00388

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

Security

Grade A, and why

health 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 12d ago.

The scan reads SKILL.md. This mod also ships 10 executable files (scripts/check_agent_context.py, scripts/check_doc_refs.py, scripts/check_maintainability.py, …), 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/health/SKILL.md · 217 lines

How it starts

The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Health: Agent-Assisted Engineering Health

Prefix your first line with 🥷 inline, not as its own paragraph.

Audit the current project's agent setup and AI coding maintainability against this framework: agent config → instruction surfaces → tools/runtime → verifiers → maintainability

Find violations. Identify the misaligned layer. Calibrate to project complexity only.

Outcome Contract

  • Outcome: a budget-aware health report that separates agent configuration risk from AI maintainability risk.
  • Done when: each finding names the misaligned layer, the concrete evidence, and a copy-pasteable action or diagnostic command.
  • Evidence: collected health script output, tracked project instructions, runtime config summaries, verifier logs, hooks/MCP surfaces, and read-only live probes when needed.
  • Output: prioritized findings with status, impact, and next action, or a clear clean bill with residual risk.

Two lanes share one report:

  • Agent config health: Codex/Claude/Pi instruction drift, permissions, hooks, MCP, skills, and memory supply chain.
  • AI maintainability health: project context surface, verifier wrapper, generated-artifact checks, hotspot ownership, and stale or misleading durable docs.

Output language: Check in order: (1) project agent instructions (AGENTS.md before runtime-specific files); (2) global agent instructions; (3) user's recent language; (4) English.

Budget posture: Start with the summary audit. Escalate automatically when the user asks for a deep, full, complete, thorough, "深入", "完整", "彻底", or "继续跑完" audit, when the user explicitly mentions AI coding code rot, Codex/Claude config drift, unclear context, missing verification, verifier output that points at stale paths, or "代码变烂", when current project instructions or remembered user preference says to run deep health checks by default, when the project is Complex, or when the summary pass exposes a critical ambiguity that cannot be resolved locally. Otherwise do not read full conversation extracts or launch inspector subagents. Tell the user before escalating because deep health audits can consume significant token quota.

Read the full file on GitHub · 217 lines

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. 12d ago First seen · 217 lines · 71 tokens per session scan A 9579f3689147

Subscribe to this mod's changes

health is a skill published in the GitHub repository sommio/qwen-omni-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 3,882 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-31.

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