explain

A guided command for explaining how a file or code section works. It covers its purpose, main logic, data flow, dependencies, design choices, and possible improvements.

In plain words
What is it for?
Use it to explain implementation details, relationships between classes or functions, external dependencies, callers, and potential problems or optimizations.
Why use it?
It helps developers understand unfamiliar code by connecting individual functions and modules to their role in the wider project.

Command

Install

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.

agentmods
npx agentmods add commands/echovic/blade-code/explain
Clone the repo
git clone --depth 1 https://github.com/echoVic/blade-code
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 219 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00219
Opus 5 $0.00004 $0.00110
Sonnet 5 $0.00002 $0.00044
Haiku 4.5 $0.00001 $0.00022

Measured 2d ago against content hash 5c87a971fa82, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.blade/commands/explain.md · 39 lines

What it actually says

请详细解释以下代码的实现:

目标文件

@$1

解释要求

请从以下几个方面进行解释:

1. 概述

  • 这个文件/模块的主要职责是什么?
  • 它在整个项目中扮演什么角色?

2. 核心逻辑

  • 主要的类/函数有哪些?
  • 它们之间的关系是什么?
  • 数据流是怎样的?

3. 关键实现

  • 有哪些重要的设计模式?
  • 有哪些值得注意的技巧?
  • 为什么这样实现?

4. 依赖关系

  • 依赖了哪些外部模块?
  • 被哪些模块依赖?

5. 潜在改进

  • 有什么可以优化的地方?
  • 有什么潜在的问题?

请用简洁的语言解释,适当使用图表(Mermaid)来辅助说明。

Changes

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.

  1. 2d ago First seen · 39 lines · 8 tokens per session scan A 5c87a971fa82

Subscribe to this mod's changes

explain is a command published in the GitHub repository echoVic/blade-code (177 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 219 once invoked, about $0.0000 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-30.