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 metago-ai/metagolifeform --skill metago-problem-tracegit clone --depth 1 https://github.com/metago-ai/metagolifeformWrote 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/metago-ai/metagolifeform/metago-problem-trace)<a href="https://agentmods.dev/skills/metago-ai/metagolifeform/metago-problem-trace"><img src="https://agentmods.dev/badge/skills/metago-ai/metagolifeform/metago-problem-trace/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/metago-ai/metagolifeform/metago-problem-trace"><img src="https://agentmods.dev/badge/skills/metago-ai/metagolifeform/metago-problem-trace.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.00054 | $0.00974 |
| Opus 5 | $0.00027 | $0.00487 |
| Sonnet 5 | $0.00011 | $0.00195 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
metago-problem-trace 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.
What it actually says
问题无限溯源（Infinite Problem Trace）
此技能基于"易霄溯源论"——任何问题都不应被预设为"无法解决"，问题的边界不在问题本身，而在追问的深度。
触发条件
- 遇到复杂问题需要深度分析根因
- 问题初步分析无法给出满意答案
- 用户要求"深入分析"或"找根本原因"
- 重大战略决策前
执行流程
步骤1：从问题表象出发
从初始问题出发，逐层追问"为什么"。
步骤2：逐层追问
L1: [初始问题] → [答案]
L2: 为什么？ → [答案]
L3: 为什么？ → [答案]
...
Ln: 为什么？ → [可解根源]
追问深度要求：
- 一般问题：至少3层
- 重大战略问题：至少7层
- 开发者指定问题：可无限追问直至找到可解根源
步骤3：终止条件
当某层答案可直接转化为解决方案时终止。
步骤4：根源领域映射
将根源问题映射到可解领域：
- 算法领域：可用数学公式、伪代码、程序实现
- 材料领域：可用化学配方、分子结构、工艺参数
- 设计领域：可用图纸、模型、设计原理
- 配方领域：可用成分比例、制备步骤
- 工艺领域：可用流程、参数、控制策略
- 管理领域：可用制度、流程、组织设计
- 策略领域：可用方法论、路径、评估标准
步骤5：闭环验证
- 生成的方案是否真正解决根源问题？
- 根源问题解决后初始问题是否解决？
输出格式
## 问题溯源链
**第1层**：为什么[问题]？
答案：[答案]
**第2层**：为什么[第1层答案]？
答案：[答案]
...
**第N层（根源）**：为什么[第N-1层答案]？
答案：**[可解根源]**
## 根源分析
- 根源问题：[root_problem]
- 映射领域：[domain]（置信度：XX%）
- 可执行方案：[solution]
## 闭环验证
- 方案是否解决根源问题？ [✅/❌]
- 根源解决后初始问题是否解决？ [✅/❌]
- 残留问题：[如有则列出]
示例
初始问题：产品良率持续下降
第1层：为什么产品良率持续下降？
答案：因为最近一周缺陷率从2%上升到5%
第2层：为什么缺陷率上升？
答案：因为焊接工序出现了问题
第3层：为什么焊接工序出现问题？
答案：因为焊料温度波动超过±5°C范围
第4层（根源）：为什么焊料温度会波动？
答案：温控传感器的校准周期是3个月，但实际精度在2个月后就开始漂移
根源问题：温控传感器校准周期过长
映射领域：工艺领域（置信度92%）
可执行方案：将传感器校准周期从3个月缩短至1.5个月，并增加每周自动精度校验
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 · 113 lines · 54 tokens per session scan A fd552d49a95a
metago-problem-trace is a skill published in the GitHub repository metago-ai/metagolifeform (4 stars, last pushed 9d ago), licensed MIT. It adds 54 tokens to every session and 974 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-31.
Other skills, from other repositories
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…
diagnose-skill-run
Diagnose a failed or suspicious Runx skill execution from receipts and harness evidence, then propose the smallest bounded improvement without replaying the failed operation.
postmortem-maker
Turn resolved-incident fragments into a traceable postmortem that separates fragment-cited facts from hypotheses, blocks publication while unknowns remain, and keeps the comms send behind a human gate.
issue-debugging
Systematic methodology for issue debugging including root cause analysis, impact mapping, tiered validation plans, and confidence assessment. Use when analyzing bugs, fixing issues, or validating fixes.
fix-bug
Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.
nio-scan
Nio code/skill execution-risk scanner. Use when the user wants to scan a file, repo, directory, or skill for execution risks — e.g. "scan this code for risks", "is this file/plugin dangerous", "check this repo for malicious code", "run nio scan on ". Focused single-purpose skill; for other Nio operations use /nio.