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 agentmods add skills/frankekn/three-kingdoms-kiro/task-templatenpx skills add frankekn/three-kingdoms-kiro --skill task-templategit 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/task-template)<a href="https://agentmods.dev/skills/frankekn/three-kingdoms-kiro/task-template"><img src="https://agentmods.dev/badge/skills/frankekn/three-kingdoms-kiro/task-template.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 | $0.00030 | $0.00320 |
| Opus 5 | $0.00015 | $0.00160 |
| Sonnet 5 | $0.00006 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
task-template 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 4d 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
任務清單輸出格式
結構
每個任務包含：
- ID — TASK-001 格式
- 標題 — 一句話描述
- 依賴 — 前置任務 ID
- 負責人 — 對應的三國 agent
- 預估 — 時間估算
- 驗收 — 完成條件
範例
## TASK-001: 建立資料庫 schema
- 依賴: 無
- 負責人: 趙雲 (zhaoyun)
- 預估: 1h
- 驗收: migration 可執行，表結構符合 design.md
- [ ] 建立 users 表
- [ ] 建立 sessions 表
- [ ] 撰寫 migration script
## TASK-002: 實作登入 API
- 依賴: TASK-001
- 負責人: 趙雲 (zhaoyun)
- 預估: 2h
- 驗收: POST /login 回傳 JWT，錯誤回傳 401
- [ ] 實作 auth.controller
- [ ] 實作 auth.service
- [ ] 單元測試
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.
- 4d ago First seen · 39 lines · 30 tokens per session scan A 23aeae2be166
task-template is a skill published in the GitHub repository frankekn/three-kingdoms-kiro (11 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 320 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 skills, from other repositories
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.