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.
git clone --depth 1 https://github.com/echoVic/blade-codeWrote 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/commands/echovic/blade-code/explain)<a href="https://agentmods.dev/commands/echovic/blade-code/explain"><img src="https://agentmods.dev/badge/commands/echovic/blade-code/explain/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/commands/echovic/blade-code/explain"><img src="https://agentmods.dev/badge/commands/echovic/blade-code/explain.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.00008 | $0.00219 |
| Opus 5.5 | $0.00003 | $0.00088 |
| Sonnet 5.5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
explain 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
请详细解释以下代码的实现：
目标文件
@$1
解释要求
请从以下几个方面进行解释：
1. 概述
- 这个文件/模块的主要职责是什么？
- 它在整个项目中扮演什么角色？
2. 核心逻辑
- 主要的类/函数有哪些？
- 它们之间的关系是什么？
- 数据流是怎样的？
3. 关键实现
- 有哪些重要的设计模式？
- 有哪些值得注意的技巧？
- 为什么这样实现？
4. 依赖关系
- 依赖了哪些外部模块？
- 被哪些模块依赖？
5. 潜在改进
- 有什么可以优化的地方？
- 有什么潜在的问题？
请用简洁的语言解释，适当使用图表（Mermaid）来辅助说明。
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 · 39 lines · 8 tokens per session scan A 5c87a971fa82
explain is a command published in the GitHub repository echoVic/blade-code (180 stars, last pushed 3d ago), licensed MIT. It adds 8 tokens to every session and 219 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
explain-code
Break down complex code into clear, understandable explanations.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.