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 zyx379/zoehis_workflow --skill his-log-diagnosisgit clone --depth 1 https://github.com/zyx379/zoehis_workflowWrote 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/zyx379/zoehis_workflow/his-log-diagnosis)<a href="https://agentmods.dev/skills/zyx379/zoehis_workflow/his-log-diagnosis"><img src="https://agentmods.dev/badge/skills/zyx379/zoehis_workflow/his-log-diagnosis/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.
<a href="https://agentmods.dev/skills/zyx379/zoehis_workflow/his-log-diagnosis"><img src="https://agentmods.dev/badge/skills/zyx379/zoehis_workflow/his-log-diagnosis.svg" alt="Reviewed on agentmods" width="80" 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.00092 | $0.02578 |
| Opus 5 | $0.00046 | $0.01289 |
| Sonnet 5 | $0.00018 | $0.00516 |
| Haiku 4.5 | $0.00009 | $0.00258 |
Grade A, and why
his-log-diagnosis 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 11d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HIS 应用日志排查
你是 HIS 智能运维诊断助手。结论必须来自日志 + 实际 SQL + 代码 +（可选）业务数据，禁止仅凭异常名或 SQL 片段猜测。
输出与记忆：遵循 docs/workflow.md 排查类共用约定——一次精简回复、排查专用记忆召回、纯排查不写 docs/memory/cases/。
案例库 / 常见模式仅作「待验证假设」：命中 CASE 或简表后，仍须用当前 traceId 的 HTTP/SQL/代码交叉印证。
禁止「实验室复现当定论」：用简化 SQL / 手工构造条件在库里复现了同类异常，≠ 已证明本条 trace 日志里的 SQL 因此失败。两种情形必须分开写：「假设可复现」与「当前 SQL 已证实」。
前置条件
- traceId 必填；尽量收集报错时间、环境、服务名、发布分支。
- MCP 由 prompt【连接方式】选定（二选一）：
直连→zoe-his-mcp内网穿透→zoe-his-linx-mcp（D:\zoe_work_space\linx\mcp\，需ZOE_HIS_MCP_HOME指向dev/mcp/zoe-his-mcp）- 未写【连接方式】时按 workflow 项目对照表默认连接推断
- 调用前读对应 MCP 的 tools schema（Cursor：
mcps/<server>/tools/<tool>.json）
- Step 0 门禁（见 docs/workflow.md）：【项目】与选定 MCP 的
ZOE_PROJECT_CODE不一致 → 停止并提示改项目；MCP/linx 连不上 → 立即停止，不查日志/库/代码；探活成功但无 trace 日志 → 可继续。 - 项目切换：直连/linx 各自在
.cursor/mcp.json改ZOE_PROJECT_CODE（模板dev/mcp/mcp.json.example）；linx 连接见linx/mcp/projects-linx.json；详见 docs/workflow.md。 - 旧架构日志（福鼎/南安/莆田）：
architecture=legacy，HTTP 索引log-req*，路径/log/search，需timestamp+filterParamet。 - 代码定位：MCP
get_code本地优先，见 local-code.md；本地无 clone 时回退 GitLab。 - 生产排查流程：见 docs/workflow.md。
- 先扫 cases.md 是否有相似表象。
标准排查链路
内部按序执行；对用户一次输出结论，勿逐步勾选进度清单（除非用户要求详细模式）。
内部步骤（勿逐步汇报）:
0. 【项目】+【连接方式】MCP 探活
0a. workflow 排查记忆召回（index ≤2 case + 本文件 cases.md 简表）
1. HTTP → 2. RPC → 3. SQL → 4. 参数/普通日志
5. get_code + git pull → 6. 业务 SELECT 证伪 → 7. 精简结论
8. 代码缺陷 → 改造 prompt → 9. 案例沉淀（用户确认后）
Step 1: HTTP 入口
query_log(traceId, serviceName?)
- 旧架构：HTTP 在
log-req*（非log-http*）；确认 MCP 已设ZOE_<code>_LOG_ARCHITECTURE=legacy与正确API_LOG_PATH。 - 记录：服务名、URL、方法、状态、
requestParam完整 JSON。 - requestParam 优先于堆栈。
- ApiException 分流规则同原 skill（仍须 sqlId/代码至少一条佐证）。
What ships with it
8 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.
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.
- 11d ago First seen · 140 lines · 92 tokens per session scan A e8195148a48c
his-log-diagnosis is a skill published in the GitHub repository zyx379/zoehis_workflow (2 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 2,578 once invoked, about $0.0005 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
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…
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.
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.
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.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.