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 ZekaiShi/evo-subagent --skill evo-route-doctorgit clone --depth 1 https://github.com/ZekaiShi/evo-subagentWrote 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/zekaishi/evo-subagent/evo-route-doctor)<a href="https://agentmods.dev/skills/zekaishi/evo-subagent/evo-route-doctor"><img src="https://agentmods.dev/badge/skills/zekaishi/evo-subagent/evo-route-doctor/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/zekaishi/evo-subagent/evo-route-doctor"><img src="https://agentmods.dev/badge/skills/zekaishi/evo-subagent/evo-route-doctor.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.00041 | $0.00306 |
| Opus 5.5 | $0.00016 | $0.00122 |
| Sonnet 5 | $0.00008 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
evo-route-doctor 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 today.
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
Evo route doctor
Find the route selected for a specific agent_key and explain it from the current workspace and registered DSH models.
- Identify the conversation workspace and the exact
agent_key. Inspect<workspace>/agents/<agent_key>.md; if absent, check whether it is one of the plugin's bundled templates (code-reviewer,researcher,wps-worker). An unknown key inherits the parent route. - For a binding or template, check the strict four-line header:
---,provider: <id>,model: <id>,---. Compare both IDs, including case, with the models registered in this DSH session. The plugin rejects an unregistered pair before starting a child. - Check whether the caller supplied a nonempty
prompt. For a built-in role, that replaces its bundled role prompt; a workspace copy uses its local role body only when the caller's prompt is empty. - Report the observed route, the file or inheritance path that selected it, the first failing check, and the smallest correction. If the live registry is unavailable, say that registration remains unverified.
Keep diagnosis read-only unless the user asks to change a binding. Do not print credentials or infer a model from its display name.
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.
- today First seen · 16 lines · 41 tokens per session scan A 0aa469b202b1
evo-route-doctor is a skill published in the GitHub repository ZekaiShi/evo-subagent (7 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 306 once invoked, about $0.0002 per session on Opus 5.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-09-28.
Other skills, from other repositories
diagnosing-bugs-zh
A diagnostic workflow for difficult bugs and performance regressions, meaning cases where software behaves incorrectly or becomes slower after a change.
dsh-hooks-authoring
Instructions for writing and debugging dsh-hooks-plugin scripts, which run during tool or session events such as before a tool call or after it finishes. These scripts return JSON decisions such as allowing, asking about, or denying an action.
error-handling
Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages. Use when designing error types, retries, circuit breakers, or user-facing failure messages in TypeScript, Python, or Go.
kubernetes-patterns
Kubernetes workload patterns, resource management, RBAC, probes, autoscaling, ConfigMap/Secret handling, and kubectl debugging for production-grade deployments. Use when writing or reviewing Kubernetes manifests, or debugging probes, RBAC, autoscaling, or resource limits.
agent-architecture-audit
Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications…
click-path-audit
Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any…