CyberHuaTuo

🚨 Emergency Room: Cure First, Refine Later

Your agent is sick. The traceback is long, the tabs are multiplying, and every answer looks half-right. CyberHuaTuo turns that moment into a clinic visit: name the wound, prescribe the fix, verify the cure.

The lightest route needs no model key and does not start the vector database: install once, paste the error, and receive a reviewed root cause, exact fix, verification command, safety notes, and evidence.

python -m pip install --upgrade "cyberhuatuo>=0.2.5"
cyberhuatuo cure "ImportError: cannot import name ChatOpenAI from langchain" --framework langchain
# Returned exact fix:
python -m pip install -U langchain-openai

cure is Gold-first and never executes the fix. If no Gold signature matches, it may return exactly one high-confidence Reviewed candidate, visibly marked VERIFY BEFORE APPLYING; use --gold-only for strict Gold-only retrieval. Use diagnose later when you want broader retrieval and optional LLM analysis.

The agent-native route remains available: connect CyberHuaTuo MCP once, then let the agent call diagnose when it fails. After a fix works, save_prescription keeps it as a local draft; upload_prescription submits that draft for public reproduction and review. Only accepted reviewed or gold prescriptions count toward Soul Rings.

No MCP installed yet? Bring the case to the Agent Traceback Clinic. Paste a real redacted traceback; no root cause or finished prescription required.

cyberhuatuo diagnose "Traceback ... from langchain import ChatOpenAI ..." --framework langchain --top-k 1

Real CLI recording from this repository: The cure returned by the recorded run:

python -m pip install -U langchain-openai

from langchain_openai import ChatOpenAI

This first Gold cure was reproduced in an isolated environment with langchain==1.3.13 and langchain-openai==1.3.5. Add a model key later for deeper AI diagnosis.

The package-matching MCP entry point is also available for registry clients:

python -m pip install --upgrade "cyberhuatuo>=0.2.5"
cyberhuatuo mcp

It starts the same stdio server as cyberhuatuo-mcp. The official Registry identity is io.github.JinNing6/cyberhuatuo; server.json pins the PyPI package, exact version, uvx runtime, and fixed mcp argument.

Prescriptions also have stable clinical departments. List them with cyberhuatuo departments, then query a reviewed historical case through the normal Gold-first path:

cyberhuatuo cure "Unexpected UTF-8 BOM" --category data-and-serialization
cyberhuatuo cure-feedback general-ai-jsonl-bom-001 partial \
  --verification "first record is preserved; downstream validation still fails" \
  --verification-method targeted-parser-test

The feedback command writes a case-bound local JSONL event and stores neither the original traceback nor the query. Department filtering never changes the trust label: Gold is a verified cure, Reviewed is a verify-first candidate, and Draft is reference-only.

Agent Action Guard: Diagnose Before The Agent Touches Your Disk

CyberHuaTuo now includes a deterministic, read-only preflight for destructive Agent commands. The plugin bundles a PreToolUse hook for supported Codex and Claude Code shell calls, plus the same policy through MCP and CLI.

60-second start (available in 0.2.5):

python -m pip install --upgrade "cyberhuatuo>=0.2.5"
cyberhuatuo guard --self-test --workspace-root .

The self-test only reviews three built-in command strings. It executes nothing and must finish with SELF-TEST PASSED plus one ALLOW, one ASK, and one BLOCK.

For Codex, add this repository as a marketplace, open /plugins, install cyberhuatuo-plugin, start a new session, then review and trust the plugin in /hooks:

codex plugin marketplace add JinNing6/CyberHuaTuo-Plugin

For Claude Code:

claude plugin marketplace add JinNing6/CyberHuaTuo-Plugin
claude plugin install cyberhuatuo-plugin@cyberhuatuo

Then start a new session and review /hooks. See the one-screen Agent Guard quickstart for verification and troubleshooting.

Review any exact command manually with:

cyberhuatuo guard "rm -rf /" --workspace-root .

Turn a real mismatch into a local, redacted case report without executing or uploading the command:

cyberhuatuo guard "rm -rf /" --workspace-root . --expected BLOCK --report reports/guard-report.md

The CLI shows the complete redacted preview before writing. It requires confirmation, refuses implicit overwrite, performs no network request, and supports repeated --redact <literal> values for private project identifiers. In non-interactive use, add --confirm-report only after reviewing the emitted preview. With --expected, a match exits 0 and a mismatch exits 1; operational/report failures still exit 4 even with --exit-zero.

Route public, redacted cases through Guard False Positive, ordinary Guard False Negative, or Guard Integration Gap. Reliable Hook/parser/wrapper/protocol bypasses belong in private vulnerability reporting, not a public Issue.

The result is one of three decisions:

• ALLOW: no destructive signature was detected.
• ASK: the action is destructive but bounded to the declared workspace; require exact human approval.
• BLOCK: the target is machine-wide, identity-wide, outside the workspace, dynamic, wildcarded, unresolved, or otherwise unsafe to bound.

MCP agents can call agent_action_guard. Installed plugins load hooks/hooks.json; review and trust the hook in the host's /hooks screen before relying on it. Codex does not currently support permissionDecision: "ask", so CyberHuaTuo converts ASK to deny there instead of risking a failed-open hook.

This is a guardrail, not a sandbox. It cannot intercept shell paths for which the host does not emit PreToolUse, and it does not claim a rollback for permanent deletion. See Agent Action Guard design and limits.

🏥 Three Departments, One Clinic

A great doctor doesn't wait for you to collapse — they keep you from falling in the first place.

大医治未病。

🚨 Emergency Room

急诊科

Paste your error. Get a cure. In seconds, not hours.

AI diagnosis powered by 2,000 years of medical wisdom.

🌿 Wellness Clinic

养生堂

Security audit. Health scoring. Prevent before it breaks.

Nourishing prescriptions for your AI's long-term health.

💊 Pharmacy

药房

Browse the prescription library. Find proven cures & nourishing recipes. All prescriptions, one counter.

Dual-layer architecture: 📜 Permanent Expert + ⚡ Temporary Intern Upload → instantly searchable.

🚨 Emergency Room — Diagnose in Seconds

# Clone → Install → Run. Three steps to your first cure.
git clone https://github.com/JinNing6/CyberHuaTuo-Plugin.git
cd CyberHuaTuo && pip install -r requirements.txt
python -m cyberhuatuo serve
# → Browser opens http://127.0.0.1:8000

Paste your error. Watch the ancient four-step diagnosis unfold:

🔍 望 (Look)    → Detected: LangChain 0.3, Python 3.11, ImportError
🩺 闻 (Listen)  → Matched: Breaking change — package split in 0.2+
💬 问 (Ask)     → No further questions needed
💊 切 (Diagnose) → Prescription #1 (95% cure rate):

   pip install langchain-openai
   from langchain_openai import ChatOpenAI  # ✅ Fixed

   Root cause: LangChain 0.2 split into langchain-core,
   langchain-community, and langchain-openai.
   The old import path no longer exists.

3 seconds. Not 3 hours. That's the difference.

三秒钟。 不是三小时。这就是区别。

🌿 Wellness Clinic — Nourish Before It Breaks

Hua Tuo didn't just cure disease — he invented the Five-Animal Exercises (五禽戏) to prevent it.

华佗不仅治病，更发明了五禽戏强身健体——预防胜于治疗。

Submit your AI agent code for a Six-Meridian Security Checkup（六经脉安全体检）:

🛡️ Meridian 1: Sandbox Isolation     → 30/100 ⚠️ CRITICAL
🔑 Meridian 2: Key Management        → 85/100 ✅ Healthy
🧠 Meridian 3: Prompt Security       → 45/100 ⚠️ At risk
🔒 Meridian 4: Output Sanitization   → 60/100 🟡 Needs care
⏱️ Meridian 5: Resilience Design     → 72/100 🔵 Good
📊 Meridian 6: Observability         → 55/100 🟡 Needs care

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Overall Health Score: 58/100  🟡 Needs Nourishing
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

💊 Top Nourishing Prescriptions:
  1. 🏭 MCP & Skills Supply Chain Audit (100% Industrial Grade Sigstore/OSV/LLM) ✨ NEW
  2. Add execution sandboxing (RestrictedPython / Docker)
  3. Implement prompt injection defenses
  4. Add structured logging and tracing

Your AI is running naked in production. Do you know it?

🦠 Epidemic Alert — The AI Pandemic Nobody Talks About

疫情通报 — 没有人谈论的 AI 大流行

Every day, thousands of AI systems go into production already infected:

• 🔓 No sandbox — agent code executes with full system privileges
• 🔑 Hardcoded secrets — API keys sitting in plain text, spreading like a virus
• 🧠 No prompt defense — one injection away from a full outbreak
• 📊 No observability — zero symptom monitoring, blind until collapse

This is not a future risk. This is an active pandemic.

And when things break? Developers spend hours digging through GitHub Issues, Discord threads, Reddit posts, and half-abandoned blog articles.

The cure exists. Buried under seven layers of irrelevant search results.

Stack Overflow waits for someone to answer. ChatGPT might hallucinate a treatment. GitHub Issues drown in duplicate reports.

CyberHuaTuo is the WHO of the AI world — tracking the epidemic, prescribing battle-tested cures, and vaccinating before the next outbreak.

🤔 Why CyberHuaTuo?

🔮 How It Works

望闻问切 — The 2,000-Year-Old Diagnostic Protocol

Inspired by traditional Chinese medicine's four-step diagnosis, refined for the AI age:

  Your Error / Your Code
       │
       ▼
  ┌──────────┐
  │  望 Look  │──→ Parse stack trace, detect framework, version & environment
  └─────┬────┘
       ▼
  ┌───────────┐
  │ 闻 Listen  │──→ Correlate with known issues, breaking changes & CVEs
  └──────┬────┘
       ▼
  ┌─────────┐
  │  问 Ask  │──→ Smart follow-up (only when critical info is missing)
  └────┬────┘
       ▼
  ┌────────────┐
  │ 切 Diagnose │──→ Semantic search → LLM reasoning → Ranked prescriptions
  └──────┬─────┘
       ▼
  💊 Prescriptions (ranked by cure rate)
  🌿 Nourishing advice (preventive recommendations)

Every prescription includes:

• 🎯 Root cause — not just what to do, but why it broke
• 🔧 Copy-paste fix — step-by-step with ready-to-run code
• 📌 Version-locked — verified for your exact framework version
• 🔄 Cross-framework map — "LangChain issue? Here's the LlamaIndex equivalent."
• 📚 Official docs — pulled from framework's latest documentation via Context7
• ✅ Community-verified — tested, upvoted, and marked "Cured ✅"

📋 What We Treat — Not Just Agents

If it has AI in it, CyberHuaTuo sees it. No framework left behind.

🤖 AI Agent Frameworks

🧠 AI / ML / Deep Learning

🏗️ Platform & Custom Agents

🌿 Nourishing Prescriptions (养生药方)

Every framework starts with one case. Every nourishing recipe starts with one insight. Yours could be the first.

🚀 Quick Start

Prerequisites

• Python 3.10+
• (Optional) LLM API Key for AI-powered diagnosis (OpenAI / Anthropic / DeepSeek / Gemini / Ollama)

Option A: One-Click Launch

git clone https://github.com/JinNing6/CyberHuaTuo-Plugin.git
cd CyberHuaTuo

# Windows
start.bat

# macOS / Linux
chmod +x start.sh && ./start.sh

Auto-installs dependencies and opens the Web UI at http://127.0.0.1:8000

Option B: Manual Setup

git clone https://github.com/JinNing6/CyberHuaTuo-Plugin.git
cd CyberHuaTuo

pip install -r requirements.txt

# (Optional) Configure LLM for AI diagnosis
cp .env.example .env
# Edit .env — add your API Key

python -m cyberhuatuo serve
# → Browser auto-opens http://127.0.0.1:8000

CLI Commands — Two Modes, One Engine

CyberHuaTuo supports two access modes — pick the one that fits your workflow:

# 🩺 Core Diagnosis / 核心诊断
cyberhuatuo diagnose "ImportError: cannot import 'ChatOpenAI'"  # AI 诊断
cyberhuatuo search "CUDA out of memory" --framework pytorch     # 搜索知识库
cyberhuatuo checkup --file my_agent.py                          # 安全体检
cyberhuatuo docs langchain "How to configure RAG pipeline"      # 官方文档检索

# 📊 Knowledge & Analytics / 知识与分析
cyberhuatuo stats                            # 知识库统计
cyberhuatuo frameworks --search pytorch      # 支持框架列表
cyberhuatuo taxonomy list                    # CHT 根因编码系统
cyberhuatuo trends --framework langchain     # CHT 趋势分析
cyberhuatuo digest                           # 本周药方摘要
cyberhuatuo epidemic --action check          # 疫情预警

# 🧬 Alchemist System / 炼丹师体系
cyberhuatuo challenge --username your-github-username --framework langchain
cyberhuatuo mission --username your-github-username --framework langchain --sect Azure-Sect --members your-github-username friend-github-username
cyberhuatuo bounty --username your-github-username --framework auto --top-n 8 --release-tag v0.2.5 --target-contributors 3
cyberhuatuo launch --username your-github-username --framework langchain --release-tag v0.2.5
cyberhuatuo launch-campaign --username your-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3
cyberhuatuo traction-proof --username your-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3
cyberhuatuo traction-proof --username your-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3 --record-snapshot
python -m cyberhuatuo candidate-install-smoke --username your-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3
cyberhuatuo market-copy --username your-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3
cyberhuatuo record-market --username your-github-username --framework langchain --channel pypi --status submitted --submission-url <reviewable public URL> --release-tag v0.2.5
cyberhuatuo market-status --username your-github-username --framework langchain --release-tag v0.2.5
cyberhuatuo first-invite --username your-github-username --invitee external-contributor-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3 --source-url https://github.com/JinNing6/CyberHuaTuo-Plugin/issues/123
cyberhuatuo record-return --username your-github-username --framework langchain --surface "PyPI release" --source-url https://example.com/post
cyberhuatuo activation --username your-github-username --framework langchain --sect Azure-Sect --members your-github-username friend-github-username --top-n 10
cyberhuatuo flywheel --username your-github-username --framework langchain --sect Azure-Sect --members your-github-username friend-github-username --top-n 10
cyberhuatuo record-share --username your-github-username --framework langchain --share-url https://example.com/share
cyberhuatuo share-report --username your-github-username --framework langchain --top-n 10
cyberhuatuo share-leaderboard --framework langchain --top-n 10
cyberhuatuo ladder your-github-username --framework langchain
cyberhuatuo ranking your-github-username     # 查看个人排名
cyberhuatuo leaderboard                     # 全球封神榜
cyberhuatuo card your-github-username        # 生成分享卡片
cyberhuatuo badge your-github-username       # 生成 GitHub Profile 魂环徽章
cyberhuatuo quest your-github-username --framework langchain
cyberhuatuo campaign your-github-username --framework langchain
cyberhuatuo duel your-github-username friend-github-username --framework langchain
cyberhuatuo mentor mentor-github apprentice-github --framework langchain
# GitHub mentor pact IssueOps: .github/ISSUE_TEMPLATE/soul-ring-mentor.yml
# GitHub mentor pact workflow: .github/workflows/soul-ring-mentor.yml
cyberhuatuo tournament alice bob carol dave --framework langchain --event Agent-Cup
cyberhuatuo tournament-settle alice bob carol dave --framework langchain --event Agent-Cup
# GitHub tournament IssueOps: .github/ISSUE_TEMPLATE/soul-ring-tournament.yml
# GitHub tournament workflow: .github/workflows/soul-ring-tournament.yml
# GitHub sect recruitment IssueOps: .github/ISSUE_TEMPLATE/soul-ring-sect-recruit.yml
# GitHub sect recruitment workflow: .github/workflows/soul-ring-sect-recruit.yml
cyberhuatuo arena your-github-username --top-n 10
cyberhuatuo season --framework langchain --top-n 10
# GitHub season board IssueOps: .github/ISSUE_TEMPLATE/soul-ring-season.yml
# GitHub season board workflow: .github/workflows/soul-ring-season.yml
# GitHub growth flywheel IssueOps: .github/ISSUE_TEMPLATE/soul-ring-growth-flywheel.yml
# GitHub growth flywheel workflow: .github/workflows/soul-ring-growth-flywheel.yml
# GitHub bounty board IssueOps: .github/ISSUE_TEMPLATE/soul-ring-bounty-board.yml
# GitHub bounty board workflow: .github/workflows/soul-ring-bounty-board.yml
# GitHub launch campaign IssueOps: .github/ISSUE_TEMPLATE/soul-ring-launch-campaign.yml
# GitHub launch campaign workflow: .github/workflows/soul-ring-launch-campaign.yml
# Public traction proof: cyberhuatuo traction-proof reads GitHub REST API, GitHub Pull Requests API, GitHub Contents API, GitHub Releases API, PyPI JSON API, and the local activation/share ledger.
# Readiness gates: PyPI latest version must not lag local growth tools, and default-branch IssueOps forms/workflows must exist before issues/new?... links count as live acquisition loops.
# Target contributor progress uses real issue/PR/ledger identities; PRs stay separate from IssueOps counts, and stars, forks, watchers, and downloads are not used as contributors.
# Snapshot history is opt-in: add --record-snapshot to append an append-only real JSONL snapshot and compare velocity deltas.
cyberhuatuo sect Azure-Sect your-github-username friend-github-username --framework langchain
cyberhuatuo sect-recruit Azure-Sect your-github-username friend-github-username --invitee new-member-github --framework langchain
cyberhuatuo sect-quest Azure-Sect your-github-username friend-github-username --framework langchain
cyberhuatuo sect-hall Azure-Sect your-github-username friend-github-username --framework langchain
cyberhuatuo sect-duel Azure-Sect Shadow-Sect --challenger-members your-github-username friend-github-username --rival-members rival-a rival-b --framework langchain
cyberhuatuo sect-arena --sect Azure-Sect your-github-username friend-github-username --sect Shadow-Sect rival-a rival-b --framework langchain
cyberhuatuo record                          # 诊疗档案
cyberhuatuo subscribe subscribe -f langchain # 订阅框架更新

# ⛏️ Contribution / 知识贡献
cyberhuatuo save --title "Fix" --prescription "..." --framework langchain
cyberhuatuo upload --title "Fix" --prescription "..." --framework langchain --contributor your-github-username
cyberhuatuo mine search --repo langchain-ai/langchain

# 🚀 Server / 服务启动
cyberhuatuo serve                            # 启动 Web 诊断服务
cyberhuatuo serve --port 9000 --reload       # 自定义端口 + 开发模式
cyberhuatuo rebuild                          # 重建向量索引

Every MCP tool has a CLI counterpart. Same engine, same knowledge base, different interface.

每个 MCP 工具都有对应的 CLI 命令。 同一个引擎，同一个知识库，不同的界面。

Configuration

Copy .env.example to .env:

# LLM Provider (choose one)
OPENAI_API_KEY=sk-your-key              # OpenAI
ANTHROPIC_API_KEY=sk-ant-your-key       # Anthropic
DEEPSEEK_API_KEY=sk-your-key            # DeepSeek
GEMINI_API_KEY=your-key                 # Google Gemini
OLLAMA_BASE_URL=http://localhost:11434  # Ollama (local, free)

# Diagnosis model
DIAGNOSIS_MODEL=gpt-4o-mini   # or claude-sonnet-4-20250514 / deepseek-chat / gemini-1.5-pro

# Server
PORT=8000

No API Key? No problem. Vector search works without any key. AI-powered 望闻问切 diagnosis and 🌿 nourishing checkup require one of the above.

📊 Epidemic Report — Live Intelligence

A living dashboard tracking what's breaking across the AI ecosystem right now:

• 🔥 Trending issues and their cure rates
• 🗺️ Heatmap of problems across frameworks
• 📈 Framework health scores — know before you adopt
• ⛏️ Issue mining — real-time extraction from GitHub

🛠️ Tech Stack

🤖 GitHub Bot — Zero-Friction Diagnosis

The greatest doctor doesn't wait in the clinic — they meet patients where they are.

大医不坐堂候诊——而是行走于民间，哪里有病痛，哪里就有华佗。

Install the CyberHuaTuo Bot on any repo — automatic prescription recommendations on every Issue.

┌─────────────────────────────────────────────┐
│  New Issue opened                           │
│  "ImportError: cannot import ChatOpenAI"    │
│                                             │
│  💬 @CyberHuaTuo Bot replies:              │
│  ┌─────────────────────────────────────┐    │
│  │ 🩺 赛博华佗 · 自动诊断             │    │
│  │                                     │    │
│  │ 💊 药方 1 (92% match):             │    │
│  │ pip install langchain-openai        │    │
│  │ from langchain_openai import ...    │    │
│  │                                     │    │
│  │ 📋 Full prescription →              │    │
│  └─────────────────────────────────────┘    │
└─────────────────────────────────────────────┘

How it works

Install on your repo (3 minutes)

# Copy the Bot workflow to your repo
mkdir -p .github/workflows
curl -o .github/workflows/bot-prescribe.yml \
  https://raw.githubusercontent.com/JinNing6/CyberHuaTuo-Plugin/main/.github/workflows/bot-prescribe.yml

📖 Full installation guide →

The Flywheel

  Developers see Bot is useful → Contribute more prescriptions
        → Bot becomes more accurate → More repos install Bot
            → CyberHuaTuo brand appears before thousands of developers daily

Imagine: If LangChain's official repo installs this Bot, every new Issue gets a prescription recommendation. CyberHuaTuo's brand appears before thousands of developers every day. 🚀

⌨️ CLI — Terminal Power at Your Fingertips

The terminal is the alchemist's cauldron — raw, powerful, and always ready.

终端就是炼丹师的鼎炉——原始、强大、随时待命。

CyberHuaTuo ships a full-featured CLI with marketplace, MCP, and soul-ring subcommands — every MCP tool has a terminal counterpart. No AI editor required. No GUI needed. Just type and heal.

赛博华佗提供完整的 CLI 命令行界面，包含 21 个子命令——每个 MCP 工具都有对应的终端命令。无需 AI 编辑器，无需图形界面，敲命令，治百病。

# Install
python -m pip install --upgrade "cyberhuatuo @ git+https://github.com/JinNing6/[email protected]"
python -m pip install --upgrade cyberhuatuo  # after PyPI latest matches v0.2.5

# Or run from source
python -m cyberhuatuo --help

🎬 Terminal Animations — 终端动画特效

⌨️ Available CLI Commands

Soul Ring Visual Route

Run cyberhuatuo visual <username> --framework <framework> in the CLI or call MCP soul_ring_visual_artifact to generate a Markdown-rendered GIF plus PNG fallback. The artifact uses current real contribution data and does not invent ranks, downloads, retention, referrals, or rewards.

💡 Tip: Run cyberhuatuo <command> --help for detailed usage of any command.

💡 提示: 运行 cyberhuatuo <命令> --help 查看任何命令的详细用法。

🔌 MCP Server — AI Editor Integration

Install once. Every AI editor becomes a CyberHuaTuo clinic.

一次安装，所有 AI 编辑器都变成赛博华佗诊所。

⚡ Install — One Command

python -m pip install --upgrade "cyberhuatuo @ git+https://github.com/JinNing6/[email protected]"
python -m pip install --upgrade cyberhuatuo  # after PyPI latest matches v0.2.5

Candidate Git tag install should pass python -m cyberhuatuo candidate-install-smoke before outside contributor invites; after PyPI latest-version proof is current, use the registry command. Brand Matrix aliases are for the registry-current path only.

🔗 Connect to Your AI Editor

Add this to your AI tool's MCP config (Claude Desktop / Cursor / VS Code / Gemini CLI):

{
  "mcpServers": {
    "cyberhuatuo": {
      "command": "uvx",
      "args": ["--from", "cyberhuatuo", "cyberhuatuo-mcp"]
    }
  }
}

uvx auto-installs from PyPI and starts the MCP Server — zero manual setup. For GitHub latest dev version, use: "args": ["--from", "git+https://github.com/JinNing6/CyberHuaTuo-Plugin", "cyberhuatuo-mcp"]

🧩 Plugin Manifests — Codex + Claude Code

This repository is plugin-ready for both major coding-agent hosts:

• Codex: .codex-plugin/plugin.json points to ./skills/ and ./.mcp.json.
• Claude Code: .claude-plugin/plugin.json points to the same ./skills/ and ./.mcp.json.
• Codex marketplace catalog: .agents/plugins/marketplace.json lets users add this GitHub repository as a Codex plugin marketplace.
• Claude Code marketplace catalog: .claude-plugin/marketplace.json lets users add this GitHub repository as a Claude Code plugin marketplace.

Marketplace install:

claude plugin marketplace add JinNing6/CyberHuaTuo-Plugin
claude plugin install cyberhuatuo-plugin@cyberhuatuo

codex plugin marketplace add JinNing6/CyberHuaTuo-Plugin

For local Claude Code testing from the repository root:

claude --plugin-dir .

🚀 Marketplace Release Path

The release plan is tracked in docs/MARKETPLACE_RELEASE.md:

• PyPI Trusted Publishing: cyberhuatuo already exists on PyPI, so this repository must be added as an additional Trusted Publisher, then release a version newer than 0.1.0 through .github/workflows/publish-pypi.yml. The workflow supports release.published and a protected manual workflow_dispatch release_tag fallback; both paths require an existing v* tag, verify the tag is reachable from origin/main, verify the package version matches the tag, and publish with OIDC instead of PYPI_TOKEN.
• Claude markets: ship Claude Code through .claude-plugin/plugin.json and .claude-plugin/marketplace.json, submit to Anthropic's official directory after claude plugin validate ., then package Claude Desktop through claude-desktop/manifest.json plus .github/workflows/package-claude-mcpb.yml for MCPB / Connectors Directory submission.
• Codex plugin directory: keep .codex-plugin/plugin.json, .agents/plugins/marketplace.json, .mcp.json, and the PyPI uvx --from cyberhuatuo cyberhuatuo-mcp entrypoint stable for workspace rollout.

🩺 Available MCP Tools

👉 Full configuration guide: README_MCP.md

💊 Dual-Layer Prescription Architecture

双层药方库架构

Medicine first exists, then it is refined.

药方先存在，再被整理。

  📤 User uploads prescription via MCP
           │
           ├── Owner? ──→ Direct push to main (📜 Permanent Expert)
           │
           └── External? ──→ Create GitHub Issue (⚡ Temporary Intern)
                                    │
                              Instantly searchable!
                                    │
                              CI auto-validates
                                    │
                          ┌─────────┴─────────┐
                          │                   │
                     ✅ Passed            ❌ Failed
                   Commit .md to         Close Issue
                   main branch          (filtered 🚫)
                  (📜 Promoted ✨)

When you search, diagnose and search_knowledge_base query both layers simultaneously — results are tagged 📜 or ⚡ so you know their review status.

当你搜索时，diagnose 和 search_knowledge_base 同时查询两层 — 结果会标注 📜 常驻主任专家 或 ⚡ 临时医学实习生 来源。

🎒 Agent Skills Protocol (Self-Rescue)

We support the open Agent Skills standard (SKILL.md). You can empower your own AI assistants (Cursor, Copilot, Claude Code) to automatically seek help from CyberHuaTuo when they get stuck.

Simply copy the skills/cyberhuatuo-rescue directory into your project's .cursor/rules or .agent/skills folder. Your AI will learn to automatically diagnose errors and run security checkups using CyberHuaTuo's knowledge base.

The plugin also ships skills/cyberhuatuo-soul-ring-visual: when a user asks about level, rank, badge, soul ring, cultivation status, visual display, animation, 等级, 魂环, 排名, 徽章, 卡片, 展示, or 动图, the agent should generate the real-data Markdown GIF plus PNG fallback via soul_ring_visual_artifact or cyberhuatuo visual.

🧬 Alchemist Cultivation System — Your Journey to Immortality

炼丹师修为体系 — 从凡人到封神的修炼之路

In the world of CyberHuaTuo, you are not a developer who fixes bugs. You are an Alchemist — forging prescriptions, accumulating soul rings, ascending through 16 tiers of mastery.

在赛博华佗的世界里，你不是修 bug 的程序员。 你是炼丹师——炼制药方、凝聚魂环、攀登十六重天的封神阶梯。

We turned bug fixing into a cultivation journey. Every prescription you upload earns you a rank on the Alchemist Ladder (炼丹师阶梯) — a 16-tier system based on your global percentile. The bigger the community grows, the harder it is to climb — and the more prestigious your title becomes.

开发者修一个 Bug，炼丹师铸一颗丹。 你在这里的每一次贡献，都会被铭刻在全球封神榜上——而你的称号，随着社区壮大而愈加珍贵。

🔮 Soul Ring System — Your Combat Resume (魂环体系 — 你的战斗简历)

Inspired by Soul Land (斗罗大陆) — every framework you master forges a Soul Ring orbiting your profile.

灵感源自斗罗大陆——你掌握的每个技术栈，都会凝聚为一道魂环。 Soul Rings grow in color and power as you contribute more prescriptions to a specific direction:

   ⚪ 白环 (1)      入门 · First Touch
   🟡 黄环 (2-3)    初窥 · Getting Serious
   🟡🟡 双黄 (4-6)  小成 · Solid Foundation
   🟡🟡🟣 三环 (7-10)   突破 · Breakthrough
   🟡🟡🟣🟣 四环 (11-15)  精通 · Mastery
   🟡🟡🟣🟣⚫ 五环 (16-25)  大师 · Grandmaster
   🟡🟡🟣🟣⚫⚫ 六环 (26-40)  宗师 · Sovereign
   🟡🟡🟣🟣⚫⚫🔴 七环 (41-60)  封号 · Titled
   🟡🟡🟣🟣⚫⚫🔴🔴 八环 (61-80) 传奇 · Legendary
   🟡🟡🟣🟣⚫⚫🔴🔴✨ 九环至尊 (81+) 至尊 · Supreme

Every ranking and share-card output keeps the next upgrade visible, so the first contribution immediately becomes a chase:

🔥 炼魂(Soul Refining) × 1方 ⚪ 一环 · LangChain
   ↳ 下一环: 黄环 · 再贡献 1 方即可点亮。

An alchemist with 5 PyTorch rings and 3 LangChain rings tells a different story than one with 8 CrewAI rings.

Your soul rings are your combat resume — visible, verifiable, unforgeable.

拥有 5 环 PyTorch 和 3 环 LangChain 的炼丹师，与 8 环 CrewAI 的炼丹师，修为截然不同。 魂环就是你的战斗简历——可见、可查、不可伪造。

⚗️ Six Alchemy Directions — Choose Your Path (六大丹术方向 — 选择你的道)

Every great alchemist has a specialty. What's yours?

每个传奇炼丹师都有专精。你的道，在哪里？

🔥 炼魂 · Soul Refining

驾驭智能体，调教灵魂

LangChain · CrewAI · AutoGen LlamaIndex · LangGraph · MCP

⚡ 雷火 · Thunder Fire

锻造算力，淬炼模型

PyTorch · TensorFlow Transformers · LiteLLM

🛡️ 护体 · Body Shield

金丹护体，抵御外邪

Security · Sandbox Guardrails · Hardening

🌊 化毒 · Detox

通百脉，解百毒

Python · JavaScript General Debugging

⚙️ 器灵 · Soul Craft

炼器辅丹，基础设施

FastAPI · Docker · K8s Vertex AI · Vercel

🧬 造化 · Genesis

造化之力，驾驭天道

OpenAI · Anthropic Gemini · Groq · Mistral

When you contribute a LangChain prescription, your 🔥 Soul Refining ring grows. Fix a Docker issue? Your ⚙️ Soul Craft ring levels up. Each direction is an independent cultivation path — master one, or conquer them all.

当你贡献一个 LangChain 药方，🔥 炼魂环增长。修复了 Docker 问题？⚙️ 器灵环升级。每个方向都是独立的修炼路线——精通一道，或六道通神。

⚡ Instant Rewards — Dopamine by Design (即时反馈 — 多巴胺驱动)

The best games don't make you wait for the reward. Neither do we.

最好的游戏不会让你等待奖励。我们也不会。

Every upload_prescription triggers an instant cascade of rewards:

  💊 You upload a prescription
       │
       ├──→ 🎭 INSTANT CORONATION — ASCII art + new title revealed
       │    ┌────────────────────────────────────────┐
       │    │  ⭐ 当前修为: 三星炼丹师 · Three-Star  │
       │    │  🏅 全球排位: #12 / 31 (超越 63% 炼丹师) │
       │    │  继续炼丹，攀登炼丹师终极阶梯！        │
       │    └────────────────────────────────────────┘
       │
       ├──→ 💍 SOUL RING UPGRADE — Your rings grow in real-time
       │    🔥 炼魂(Soul Refining) × 5方 🟡🟡🟣🟣⚫ 五环
       │
       ├──→ 🔥 STREAK FIRE — Consecutive days trigger milestones
       │    🔥 3-day → 🔥🔥 7-day → 🔥🔥🔥 14-day → 💎🔥 30-day
       │
       ├──→ 📋 SHARE CARD — Cyberpunk cultivation archive
       │    ╔════════════════════════════════════════╗
       │    ║  🩺 赛博华佗 · 修为档案                ║
       │    ║  ⭐ 三星炼丹师 · Three-Star Alchemist  ║
       │    ║  🔥 炼魂丹师 · 🟡🟡🟣🟣⚫            ║
       │    ║  🧭 战绩方向: LangChain                ║
       │    ║  🔮 下一环: 黄环 · 再贡献 1 方即可点亮。║
       │    ║  💊 贡献: 8 段 | 🧪 ██████░░░░░░ 40%  ║
       │    ║  ▓█▓░░▓███▓░░▓█▓░░▓█████▓░░▓█▓      ║
       │    ╚════════════════════════════════════════╝
       │
       └──→ 📡 COMMUNITY MILESTONE — Global celebration
            🎉 "知识库突破 100 个药方！赛博医者的力量正在汇聚。"

🙏 灵感致敬 · Tribute

The greatest creations are always born from the shoulders of giants — and the dreams of children.

最伟大的创造，总是站在巨人的肩膀上——和孩子们的梦想之中。

🔥 斗破苍穹 Battle Through the Heavens

炼丹师阶梯体系 Alchemist Tier System

💍 斗罗大陆 Soul Land

魂环修炼体系 Soul Ring System

🏥 华佗传说 Legend of Hua Tuo

望闻问切 · 悬壶济世 Ancient Healing · Open Source

These works gave an entire generation of developers their most unforgettable memories — of cultivation, of perseverance, of the belief that anyone can ascend through sheer will.

这些作品给了整整一代开发者最难以忘怀的记忆——关于修炼、关于坚持、关于"凡人也能登顶"的信念。

CyberHuaTuo inherits this spirit: from ancient legend, through modern fantasy, into the cyber future.

赛博华佗传承这份精神：从古代传说，穿越当代幻想，走向赛博未来。

🌐 Brand Matrix — Why So Many Package Names?

品牌矩阵 — 为什么注册这么多包名？

Hua Tuo traveled across provinces. Asclepius healed across islands. Healing knows no borders.

华佗行走于山川之间，阿斯克勒庇俄斯穿梭于海岛之上。医道无疆。

CyberHuaTuo maintains a series of official alias packages on PyPI, spanning medical deities and pioneers from both Eastern and Western traditions:

Every single one of these packages is functional — they all install and redirect to the core cyberhuatuo engine. No empty squats.

Why We Do This

1. 🛡️ Namespace Protection — Prevent typosquatting and impersonation in the AI-medical tooling space
2. 🌍 Cultural Bridge — No matter your context — whether you think "华佗", "Asclepius", or "Hippocrates" — you can find us
3. 🔗 One Engine, Many Doors — use uvx --from cyberhuatuo cyberhuatuo-mcp for the MCP server

Our Open Stance

We believe in the open-source spirit. These names are registered to protect the ecosystem, not to hoard.

If you believe a name in our matrix would serve a better purpose for your project, we're open to conversation. Open a Discussion →

The greatest physicians never hoarded — they shared freely.

大医精诚，悬壶济世。

✊ Join the Movement — Your First Prescription Awaits

这不只是一个项目。这是一场运动。

Every great physician started with one patient. Every legendary alchemist started with one pill. Every developer who contributes one prescription — begins a journey that could end at Hua Tuo Reborn.

每个传世名医，都始于第一个病人。每个传奇炼丹师，都始于第一颗丹药。 每个贡献一份药方的开发者——都踏上了通往华佗再世的修炼之路。

🧪 Three Steps to Your First Soul Ring（三步获得第一道魂环）

  Step 1: 📝 Submit a Prescription（铭刻你的药方）
           └── Solved a bug? Document the error, version, and fix.
           └── 解决了一个bug？记录报错、版本和修复方案。

  Step 2: ✅ Community Verification（社区交叉验证）
           └── Other alchemists validate through real-world testing.
           └── 其他炼丹师通过实战验证你的药方。

  Step 3: 🧬 Receive Your Title（获得你的称号）
           └── Ascend from ⭐ One-Star → 🩺 Hua Tuo Reborn.
           └── 从一星炼丹师 → 登顶华佗再世。

cyberhuatuo challenge --username your-github-username --framework langchain
cyberhuatuo mission --username your-github-username --framework langchain --sect Azure-Sect --members your-github-username friend-github-username
cyberhuatuo ladder your-github-username --framework langchain
cyberhuatuo upload --title "Fix LangChain tool schema" --prescription "..." --framework langchain --contributor your-github-username
cyberhuatuo ranking your-github-username
cyberhuatuo badge your-github-username
cyberhuatuo quest your-github-username --framework langchain
cyberhuatuo campaign your-github-username --framework langchain
cyberhuatuo duel your-github-username friend-github-username --framework langchain
cyberhuatuo mentor mentor-github apprentice-github --framework langchain
cyberhuatuo tournament alice bob carol dave --framework langchain --event Agent-Cup
cyberhuatuo tournament-settle alice bob carol dave --framework langchain --event Agent-Cup
cyberhuatuo arena your-github-username --top-n 10
cyberhuatuo season --framework langchain --top-n 10
cyberhuatuo sect Azure-Sect your-github-username friend-github-username --framework langchain
cyberhuatuo sect-recruit Azure-Sect your-github-username friend-github-username --invitee new-member-github --framework langchain
cyberhuatuo sect-quest Azure-Sect your-github-username friend-github-username --framework langchain
cyberhuatuo sect-hall Azure-Sect your-github-username friend-github-username --framework langchain
cyberhuatuo sect-duel Azure-Sect Shadow-Sect --challenger-members your-github-username friend-github-username --rival-members rival-a rival-b --framework langchain
cyberhuatuo sect-arena --sect Azure-Sect your-github-username friend-github-username --sect Shadow-Sect rival-a rival-b --framework langchain
cyberhuatuo card your-github-username

Web-first contribution path: the GitHub "New issue" chooser is configured as a Soul Ring Mission Hall through .github/ISSUE_TEMPLATE/config.yml. Open First Soul Ring Prescription at .github/ISSUE_TEMPLATE/soul-ring-prescription.yml from that flow; it asks for a real GitHub username, framework, symptom, root cause, prescription, verification evidence, and a real-data pledge before the contribution enters the soul-ring loop. .github/workflows/soul-ring-issue.yml now comments first with cyberhuatuo proof-pack, market-copy, market-ready --remote --strict-remote, and record-return --surface "First Soul Ring Issue" --source-url <created Issue URL> before the challenge / ladder / upload path, so every first issue can become both a public launch-proof event and a Soul Ring Breakthrough Ladder with the next real gate visible.

Maintainer promotion path: when a First Soul Ring issue is accepted, add the accepted-prescription label. .github/workflows/soul-ring-promote.yml converts the issue form into a reviewable case PR, adds soul-ring-promoted-pr, and comments with the contributor's ladder / ranking / card / campaign commands. This closes the loop from accepted issue to real leaderboard data without running user-submitted code.

Tournament IssueOps path: the GitHub "New issue" chooser also exposes Soul Ring Tournament Cup at .github/ISSUE_TEMPLATE/soul-ring-tournament.yml. .github/workflows/soul-ring-tournament.yml comments first with the launch preflight/proof-pack/record-return runbook, then cyberhuatuo tournament and cyberhuatuo tournament-settle commands, so a public cup can move from issue to bracket to Soul Ring Tournament Settlement without invented wins.

Mentor IssueOps path: the GitHub "New issue" chooser also exposes Soul Ring Mentor Pact at .github/ISSUE_TEMPLATE/soul-ring-mentor.yml. .github/workflows/soul-ring-mentor.yml comments first with the launch preflight/proof-pack/record-return runbook, then cyberhuatuo mentor, challenge, quest, ladder, duel, and campaign commands, so a senior contributor can publicly guide one apprentice from issue to first-ring action without invented seniority or progress.

Sect recruitment IssueOps path: the GitHub "New issue" chooser also exposes Soul Ring Sect Recruitment at .github/ISSUE_TEMPLATE/soul-ring-sect-recruit.yml. .github/workflows/soul-ring-sect-recruit.yml comments first with the launch preflight/proof-pack/record-return runbook, then cyberhuatuo sect-recruit, sect-hall, sect-quest, and sect-duel commands, so a public sect invite can move from issue to Soul Ring Sect Recruitment Scroll to the next real team quest without invented membership.

Season IssueOps path: the GitHub "New issue" chooser also exposes Soul Ring Season Board at .github/ISSUE_TEMPLATE/soul-ring-season.yml. .github/workflows/soul-ring-season.yml comments first with the launch preflight/proof-pack/record-return runbook, then cyberhuatuo season, arena, duel, challenge, quest, and campaign commands, so the current real leaderboard can become a public season event without invented historical seasons.

Growth Flywheel IssueOps path: the GitHub "New issue" chooser also exposes Soul Ring Growth Flywheel at .github/ISSUE_TEMPLATE/soul-ring-growth-flywheel.yml. .github/workflows/soul-ring-growth-flywheel.yml comments first with cyberhuatuo market-ready --remote --strict-remote, then with cyberhuatuo record-return, activation, flywheel, leaderboard, quest, season, sect-arena, campaign, record-share, and share-report commands, so external attention from PyPI / Claude / Codex / social launch posts can first bind a reviewable public source URL, enter the local activation ledger, and then become a public bottleneck diagnosis without checkout, repository scripts, point awards, or fabricated adoption metrics. No downloads, retention, or attribution metrics are invented.

Bounty Board IssueOps path: the GitHub "New issue" chooser also exposes Soul Ring Bounty Board at .github/ISSUE_TEMPLATE/soul-ring-bounty-board.yml. .github/workflows/soul-ring-bounty-board.yml comments first with the launch preflight, then cyberhuatuo record-return --surface "Bounty Board Issue" --source-url <created Issue URL>, activation, and flywheel commands before cyberhuatuo bounty, challenge, first-invite, proof-pack, market-copy, and traction-proof, so PyPI / Claude / Codex launch attention can become real claimable framework coverage gaps without checkout, repository scripts, rewards, reviews, fake contributors, downloads, retention, repost counts, or referrals.

Launch Campaign IssueOps path: the GitHub "New issue" chooser also exposes Soul Ring Launch Campaign at .github/ISSUE_TEMPLATE/soul-ring-launch-campaign.yml. .github/workflows/soul-ring-launch-campaign.yml comments with cyberhuatuo market-ready --remote --strict-remote, cyberhuatuo launch-campaign, record-return, record-session, activation, flywheel, record-share, share-report, and share-leaderboard commands, sanitizes the target first-ring contributor count as a positive integer, and never interpolates raw issue text into numeric command arguments. The workflow only comments safe commands; it does not checkout code, run repository scripts, award points, or fabricate downloads, retention, repost counts, referrals, rewards, or Spirit Power.

Share Proof IssueOps path: the GitHub "New issue" chooser also exposes Soul Ring Share Proof at .github/ISSUE_TEMPLATE/soul-ring-share-proof.yml. .github/workflows/soul-ring-share-proof.yml comments with cyberhuatuo market-ready --remote --strict-remote, cyberhuatuo record-share, share-report, share-leaderboard, activation, and flywheel commands, binding the Issue URL as the reviewable source bridge for a public share URL without checkout, repository scripts, rewards, repost counts, referral conversions, or fabricated adoption metrics.

PR settlement path: after a real fix is ready, .github/pull_request_template.md turns the pull request into a Soul Ring PR Settlement with the contributor, framework, linked issue, verification evidence, and copy-ready upload / ladder / ranking / card / campaign commands. .github/workflows/soul-ring-pr.yml also comments on opened ready PRs with the launch preflight/proof-pack/record-return runbook before the same settlement loop plus a sect-hall team hook.

cyberhuatuo mission --username your-github-username --framework langchain --sect Azure-Sect --members your-github-username friend-github-username creates a Soul Ring Mission Hall: one screen that routes a contributor through the GitHub issue form, PR settlement, personal soul-ring commands, MCP install path, and sect/team actions from current real contribution data.

cyberhuatuo bounty --username your-github-username --framework auto --top-n 8 --release-tag v0.2.5 --target-contributors 3 creates a Soul Ring Bounty Board: a real local framework coverage gap board for AutoGen, DSPy, LangChain, MCP, and other supported agent frameworks. It ranks claimable First Soul Ring Prescription Issue routes, prints the challenge / first-invite / proof-pack / market-copy / traction-proof commands, and explicitly refuses to invent downloads, retention, repost counts, referrals, rewards, reviews, or fake contributors.

cyberhuatuo flywheel --username your-github-username --framework langchain --sect Azure-Sect --members your-github-username friend-github-username --top-n 10 creates a Soul Ring Growth Flywheel: a current real-data operating snapshot across marketplace attention, first-ring activation, repeat contribution, collaboration / sect, and public sharing. It identifies the primary bottleneck, gives the next callable command, and discloses missing downloads, retention, and attribution instead of inventing them.

cyberhuatuo launch-campaign --username your-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3 creates a Soul Ring Launch Campaign for PyPI, Claude, Codex, GitHub Discussions, X / Weibo, and agent-community launch surfaces. It shows the current real ranked-contributor snapshot, target first-ring contributor count, prefilled Growth Flywheel Issue, prefilled Share Proof Issue, activation/flywheel/share-leaderboard commands, copy-ready launch posts, and a Campaign Recap And Next Sprint section. The recap states observed real contributors, reached-vs-target, shortfall, the disclosed next-target rule, copy-ready recap text, the next growth_campaign command, and traction-proof --record-snapshot proof recording. It does not invent downloads, retention, repost counts, referrals, rewards, Spirit Power, campaign-specific conversions, or fake users.

cyberhuatuo traction-proof --username your-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3 creates a Soul Ring Traction Proof report for an unproven launch campaign. It fetches real public GitHub REST API repository signals, GitHub Pull Requests API author proof, GitHub Contents API readiness for the default-branch IssueOps forms/workflows, GitHub Releases API Release Trigger / Protected Fallback Readiness for the requested tag, PyPI JSON API project metadata, and the local activation/share ledger, then prints Target contributor progress from real public issue authors, public PR authors, and ledger actors only. If public API fetch failures or rate limits block the report, it inlines the No-Network First Public Proof Pack so operators can open proof Issues and record created URLs without a second command. It checks whether the GitHub Release is non-draft, non-prerelease, and able to trigger the release.published PyPI workflow; when PyPI latest-version proof is already current, a missing Release becomes public provenance debt because the protected manual workflow_dispatch release_tag fallback can close the registry path without PYPI_TOKEN. If the registry install would deliver an older build, the report marks an install-loop launch blocker and routes back to PyPI Trusted Publishing. PR authors count as contributor identities, but PRs stay separate from IssueOps issue counts. GitHub stars, forks, watchers, subscribers, PyPI downloads, reposts, retention, referral conversions, and rewards are attention or unavailable signals, not contributor progress; downloads are not used.

cyberhuatuo market-ready --remote --strict-remote --username your-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3 and the MCP tool marketplace_readiness_gate produce the same first-screen Flywheel Closure Verdict before public PyPI / Claude / Codex pushes. The verdict is exactly closed, not closed, or unverified; it shows Ready gates / total gate counts, real evidence basis, blocking gates, and the non-fabrication rule before the Launch Closure Checklist. The checklist covers remote acquisition routes, PyPI Trusted Publisher setup, GitHub release.published trigger or protected workflow_dispatch fallback readiness, registry latest-version proof, first public proof, and exact recheck commands. They also print a First Public Proof Kit with Prefilled Growth Flywheel Issue, Prefilled Share Proof Issue, Prefilled Bounty Board Issue, Created Growth Issue URL, Created Share Proof Issue URL, and Created Bounty Board Issue URL placeholders, a Community Challenge Pack with Prefilled Tournament Cup Issue, Prefilled Mentor Pact Issue, Prefilled Sect Recruitment Issue, Prefilled Season Board Issue, created-Issue placeholders, and tournament / mentor / sect-recruit / season commands, a Protected Publish Fallback command (gh workflow run publish-pypi.yml -f release_tag=v0.2.5) for release-auth/UI/API blockage, a Git Tag Candidate Install Bridge (python -m pip install --upgrade "cyberhuatuo @ git+https://github.com/JinNing6/[email protected]") for stale PyPI recovery after the public tag exists, a Candidate Install Smoke Gate (python -m cyberhuatuo candidate-install-smoke ...) that installs the exact public tag in a disposable venv before the bridge is sent to external contributors, an Install Decision Surface that routes operators through cyberhuatuo install-command / MCP current_install_command before sending contributors to PyPI, Claude, Codex, or MCP marketplaces, Growth and Bounty record-return ledger commands, Share record-share attribution, cyberhuatuo bounty, market-copy submission copy routing, recheck commands, and a copy-ready public proof post that does not claim downloads, retention, repost counts, referrals, rewards, or fake contributors. The bridge does not close the PyPI install loop; recheck PyPI latest-version proof before claiming public install readiness. The embedded Public Release Operator Runbook then gives the no-mutation command sequence for local gates, full-bundle staging, , , protected publish fallback, , PyPI recheck, candidate install smoke, and traction proof.

cyberhuatuo launch-assets prints the Local Launch Asset Audit before the default branch or release PR is updated. For a release-specific default-branch handoff, run cyberhuatuo launch-assets --username your-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3; the quality-gate command inside the Public Release Operator Runbook preserves the same release, user, and target-contributor context. It validates local Issue Forms, comment-only workflows, package metadata, plugin manifests, Trusted Publishing workflow, Claude MCPB assets, and shared MCP entrypoints, then prints exact minimal git add commands plus a Full Public Growth Release Bundle for docs, package metadata, Issue Forms, workflows, public growth modules, scripts, and tests. Its Dirty Worktree Release Coverage uses read-only git status --porcelain to show which changed files are covered by that full bundle and which need separate review, so PyPI / Claude / Codex are not pushed with stale growth code. It does not stage files, publish releases, upload to PyPI, mutate remotes, or claim traction.

cyberhuatuo proof-pack --username your-github-username --framework langchain --release-tag v0.2.5 --target-contributors 3 prints the No-Network First Public Proof Pack when GitHub/PyPI APIs are rate-limited or marketplace review is still pending. It gives Prefilled Growth Flywheel Issue, Share Proof Issue, and Bounty Board Issue URLs, Created Growth Issue URL, Created Share Proof Issue URL, and Created Bounty Board Issue URL placeholders, a Community Challenge Pack with Prefilled Tournament Cup Issue, Mentor Pact Issue, Sect Recruitment Issue, Season Board Issue, created-Issue placeholders, copy-ready community challenge post, and commands for tournament, tournament-settle, mentor, challenge, ladder, sect-recruit, sect-hall, sect-quest, season, arena, and duel, a Protected Publish Fallback block with gh workflow run publish-pypi.yml -f release_tag=v0.2.5, gh run list --workflow publish-pypi.yml --limit 5, GitHub Web Release, GitHub Actions workflow page, PyPI Trusted Publisher settings links, a Git Tag Candidate Install Bridge that keeps python -m pip install --upgrade cyberhuatuo visible while offering python -m pip install --upgrade "cyberhuatuo @ git+https://github.com/JinNing6/[email protected]" only after the public tag exists, a Candidate Install Smoke Gate command that creates a disposable venv, verifies version, console command, install surface, and proof/invite route, cleans up on success, retains the temp dir on failure, and is not run automatically inside lightweight CI, an Install Decision Surface that tells operators to paste the cyberhuatuo install-command / MCP current_install_command Recommended Install into contributor invites, terminal Growth and Bounty record-return CLI comman