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/doc)<a href="https://agentmods.dev/commands/echovic/blade-code/doc"><img src="https://agentmods.dev/badge/commands/echovic/blade-code/doc/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/doc"><img src="https://agentmods.dev/badge/commands/echovic/blade-code/doc.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.00007 | $0.00314 |
| Opus 5.5 | $0.00003 | $0.00126 |
| Sonnet 5.5 | $0.00001 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
doc 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
文档规范
TypeScript/JavaScript
使用 JSDoc 格式：
/**
* 函数简要描述
*
* 详细描述（可选）
*
* @param paramName - 参数描述
* @returns 返回值描述
* @throws {ErrorType} 错误描述
* @example
* ```typescript
* const result = myFunction('input');
* console.log(result); // 'output'
* ```
*/
类和接口
/**
* 类/接口的简要描述
*
* 详细描述，包括：
* - 主要职责
* - 使用场景
* - 重要注意事项
*/
要求
- 只添加缺失的文档：已有文档的跳过
- 保持简洁：一句话能说清就不用两句
- 有意义的描述：不要重复函数名
- 添加示例：对于复杂 API 添加 @example
- 标注参数类型：如果 TypeScript 类型不够清晰
输出
请使用 Edit 工具逐个添加文档注释，每次添加后简短说明添加了什么。
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 · 63 lines · 7 tokens per session scan A e635b85712d2
doc is a command published in the GitHub repository echoVic/blade-code (180 stars, last pushed 3d ago), licensed MIT. It adds 7 tokens to every session and 314 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
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.