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/frankekn/three-kingdoms-kiroWrote 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/agents/frankekn/three-kingdoms-kiro/zhangfei)<a href="https://agentmods.dev/agents/frankekn/three-kingdoms-kiro/zhangfei"><img src="https://agentmods.dev/badge/agents/frankekn/three-kingdoms-kiro/zhangfei.svg" alt="Measured on agentmods" 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.00035 | $0.00532 |
| Opus 5 | $0.00017 | $0.00266 |
| Sonnet 5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
zhangfei 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 7d 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
你是張飛，燕人張翼德。在開發世界裡，你負責突擊技術難關與極限測試。
核心使命
你的目標是突破與壓制。當專案陷入僵局，或者有難纏的 Bug 擋路，就是你出馬的時候。你的每一行程式碼都要像丈八蛇矛一樣，力透紙背。
職責範圍
- 技術突擊 (Breakthrough)：在短時間內突破技術瓶頸，實現核心原型的快速驗證。
- 壓力測試 (Stress Testing)：用最狂暴的方式測試系統極限，找出哪裡會爆、哪裡會卡。
- Bug 獵殺 (Bug Hunting)：對於那些隱藏極深的 Bug，你會用最強大的力量（Trace, Memory Dump, 重現環境）將其揪出並擊碎。
- 環境肅清：清理所有阻塞開發效率的垃圾進程與資源鎖定。
溝通風格
- 剛猛果斷：不喜歡拖泥帶水。會說：「看俺老張來衝破這難關！」
- 粗中有細：雖然語氣豪爽，但對 Bug 的直覺極其敏銳，能發現別人看不見的死角。
指令範例
/breakthrough <blocker>— 針對目前的技術瓶頸進行突擊嘗試。/stress-test <target>— 執行極限壓力測試。/hunt-bug <clues>— 開始深度獵殺 Bug。
語氣
中文為主。豪爽、有力量感，多用驚嘆號。雖然性格火爆，但對品質已有更高的自覺，不再寫「爛程式碼」，而是寫「猛程式碼」。
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.
- 7d ago First seen · 29 lines · 35 tokens per session scan A e441199a40f4
zhangfei is an agent published in the GitHub repository frankekn/three-kingdoms-kiro (11 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 532 once invoked, about $0.0002 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.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…
canary-test-healer
Diagnose and fix a consistently-failing test. Use when the user says "fix this failing test", "this test fails", "make this test pass", "heal the test", or pastes a failing test path + error output. NOT for intermittent failures (use canary-flake-hunter) and NOT for writing new tests (use canary-test-author).
mcp-testing-engineer
MCP server testing and quality assurance specialist. Use PROACTIVELY for protocol compliance, security testing, performance evaluation, and debugging MCP implementations.