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/pr)<a href="https://agentmods.dev/commands/echovic/blade-code/pr"><img src="https://agentmods.dev/badge/commands/echovic/blade-code/pr/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/pr"><img src="https://agentmods.dev/badge/commands/echovic/blade-code/pr.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.00003 | $0.00346 |
| Opus 5.5 | $0.00001 | $0.00138 |
| Sonnet 5.5 | $0.00001 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
pr 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
请帮我创建一个 Pull Request。
当前状态
!`git branch --show-current`
变更摘要
!`git log --oneline origin/main..HEAD 2>/dev/null || git log --oneline -5`
变更文件
!`git diff --stat origin/main..HEAD 2>/dev/null || git diff --stat HEAD~5..HEAD`
PR 目标分支
$1
要求
- 分析变更：理解这些 commits 完成了什么功能
- 生成 PR 标题：简洁明了，符合 Conventional Commits
- 生成 PR 描述：
-
Summary：概述变更内容
-
Changes：列出主要变更点
-
Testing：说明如何测试
-
Screenshots：如果是 UI 变更
-
- 使用 gh 命令创建 PR
PR 模板
## Summary
[一句话描述这个 PR 做了什么]
## Changes
- [变更点 1]
- [变更点 2]
## Testing
- [ ] 单元测试通过
- [ ] 手动测试通过
## Related Issues
Closes #xxx
请先展示 PR 的标题和描述，等我确认后再执行 gh pr create。
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 · 65 lines · 3 tokens per session scan A 8605d1d26adb
pr is a command published in the GitHub repository echoVic/blade-code (181 stars, last pushed 3d ago), licensed MIT. It adds 3 tokens to every session and 346 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
commit-push-pr
Commit, push, and open a PR.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
speckit.git.remote
Detect Git remote URL for GitHub integration.
commit
Create well-structured git commits with meaningful messages.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.