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.
npx skills add frankekn/three-kingdoms-kiro --skill refactor-cleangit 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/skills/frankekn/three-kingdoms-kiro/refactor-clean)<a href="https://agentmods.dev/skills/frankekn/three-kingdoms-kiro/refactor-clean"><img src="https://agentmods.dev/badge/skills/frankekn/three-kingdoms-kiro/refactor-clean.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.00025 | $0.00330 |
| Opus 5 | $0.00013 | $0.00165 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
refactor-clean 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
重構清理
步驟
1. 偵測 Dead Code
npx knip # JS/TS unused exports/files/deps
npx depcheck # unused npm deps
找不到工具時用 grep 搜尋 exports 有無被 import。
2. 分級
| 級別 | 範例 | 處理 |
|---|---|---|
| SAFE | 未使用的 utility、test helper | 直接刪 |
| CAUTION | component、API route、middleware | 先確認無動態 import |
| DANGER | config、entry point、type def | 調查後再動 |
3. 逐一刪除（每次一個）
- 跑全部測試 → 確認 baseline 全綠
- 刪除一個 dead code
- 重跑測試 → 通過就繼續，失敗就
git checkout -- <file>
4. 合併重複
- 相似度 >80% 的函式 → 合併
- 無用的 re-export → 移除
- 只是 wrapper 沒加值 → inline
原則
- 一次刪一個，不確定就跳過
- 清理和重構分開做
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 · 37 lines · 25 tokens per session scan A 31cfdb125a9b
refactor-clean is a skill published in the GitHub repository frankekn/three-kingdoms-kiro (11 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 330 once invoked, about $0.0001 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 skills, from other repositories
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
gsd-ns-review
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
superlint
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.