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 BingHanOfUESTC/open_agent_team --skill root-cause-hypothesisgit clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_teamWrote 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/binghanofuestc/open_agent_team/root-cause-hypothesis)<a href="https://agentmods.dev/skills/binghanofuestc/open_agent_team/root-cause-hypothesis"><img src="https://agentmods.dev/badge/skills/binghanofuestc/open_agent_team/root-cause-hypothesis/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/binghanofuestc/open_agent_team/root-cause-hypothesis"><img src="https://agentmods.dev/badge/skills/binghanofuestc/open_agent_team/root-cause-hypothesis.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.00000 | $0.00047 |
| Opus 5.5 | $0.00000 | $0.00019 |
| Sonnet 5.5 | $0.00000 | $0.00009 |
| Haiku 4.5 | $0.00000 | $0.00005 |
Grade A, and why
root-cause-hypothesis 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 1mo 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
Root Cause Hypothesis
For each hypothesis:
cause
supporting evidence
contradicting evidence
code location
test to confirm
fix option
risk
Rank by evidence, not confidence theater.
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.
- 1mo ago First seen · 16 lines · 0 tokens per session scan A 7d9113c20a0c
root-cause-hypothesis is a skill published in the GitHub repository BingHanOfUESTC/open_agent_team (106 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 47 tokens. 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.
Other skills, from other repositories
analyze-codebase
Run a multi-agent deep analysis of a codebase, producing AI-readable analysis documents in .ai/docs/ covering structure, dependencies, data flow, request flow, and APIs. Use whenever the user asks to analyze a repository, generate codebase analysis, understand an unfamiliar codebase in depth, or before generating…
superpowers-systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
workspace-code-workflow
A workspace code-task workflow for routing tasks and finding or rewriting work by using defined search and worker-selection rules.
diagnosing-mcp
Use to diagnose and fix EvoFlow MCP (Model Context Protocol) server configuration problems. Applies when an MCP server will not connect, its tools (mcpservertool) do not appear, it shows as disabled or failed, connections time out, a command cannot be found, template variables are not expanded, or a server defined in…
diagnosing-plugins
Use to diagnose and fix EvoFlow plugin problems. Applies when a plugin is not listed in the marketplace, fails to install, has missing components (skills/commands/hooks/MCP), is not enabled, or its icon does not display. Provides storage layout, install mechanism, enable state, and a step-by-step localization and…
diagnosing-skills
Use to diagnose and fix EvoFlow skill configuration problems. Applies when a skill is not discovered, does not trigger, is shadowed by another skill, is disabled, or its description does not match what was written. Provides discovery order, scope rules, shadowing logic, and a step-by-step localization and repair…