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 Stanshy/AgentHub --skill task-delegationgit clone --depth 1 https://github.com/Stanshy/AgentHubWrote 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/stanshy/agenthub/task-delegation)<a href="https://agentmods.dev/skills/stanshy/agenthub/task-delegation"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/task-delegation/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/skills/stanshy/agenthub/task-delegation"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/task-delegation.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.00020 | $0.00871 |
| Opus 5.5 | $0.00008 | $0.00348 |
| Sonnet 5.5 | $0.00004 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
task-delegation 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
任務拆解與分派
在開發計畫書第 6 節建立任務表，同時產生 .tasks/sprint-{N}/TN-xxx.md 檔案。
使用方式
/task-delegation
執行步驟
-
讀取當前 Sprint 的 dev-plan： !
ls -t proposal/sprint*-dev-plan.md 2>/dev/null | head -1 | xargs cat 2>/dev/null || echo "找不到 dev-plan" -
根據第 3 節（檔案變更清單）和技術方案，拆解任務
-
更新 dev-plan 第 6 節任務表：
| 任務 | 說明 | 負責 | 依賴 | 預估 |
|------|------|------|------|------|
| T1 | ... | backend-architect | — | 1h |
-
取得真實時間（必要，不可跳過）： !
node -e "console.log(new Date().toISOString())"⚠️ 禁止自行編造時間。將輸出存為
$NOW供後續步驟使用（建立時間與事件紀錄 timestamp）。 -
為每個任務建立
.tasks/sprint-{N}/TN-{kebab-case-name}.md：
⚠️ Sprint 子目錄規則：任務檔案必須放在對應 Sprint 的子目錄下。
- Sprint 1 的任務 →
.tasks/sprint-1/T1-xxx.md- Sprint 2 的任務 →
.tasks/sprint-2/T3-xxx.md- 如果目錄不存在，先建立：
mkdir -p .tasks/sprint-{N}- 禁止 直接放在
.tasks/根目錄（會導致跨 Sprint ID 衝突）
格式規範（系統解析依賴，務必遵守）
| 欄位 | 格式 | 說明 |
|---|---|---|
| ID | TN |
T + 數字，如 T1, T2, T10 |
| Sprint | Sprint N |
必須用 Sprint N 格式（如 Sprint 1），系統用此名稱對應 DB 中的 Sprint UUID |
| 狀態 | 英文小寫 | 初始值為 assigned（L1 拆解時已知指派對象） |
| 優先級 | P0 / P1 / P2 |
— |
| 建立時間 | ISO 8601 | 如 2026-03-26T12:00:00.000Z |
| 依賴 | 逗號分隔 ID | 如 T1,T3，無則填 — |
# {任務標題}
| 欄位 | 值 |
|------|-----|
| ID | TN |
| 專案 | {專案名} |
| Sprint | Sprint {N} |
| 指派給 | {agent-id} |
| 優先級 | P0/P1 |
| 狀態 | assigned |
| 依賴 | {依賴任務 ID，無則填 —} |
| 預估 | {預估工時，無則填 —} |
| 建立時間 | $NOW |
---
## 任務描述
{詳細描述}
## 驗收標準
- [ ] ...
---
## 事件紀錄
### $NOW — 建立任務（assigned）
由 L1 透過 /task-delegation 建立
- 畫出依賴圖（ASCII art）
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 · 87 lines · 20 tokens per session scan A 92007987fbd0
task-delegation is a skill published in the GitHub repository Stanshy/AgentHub (204 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 871 once invoked, about $0.0001 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 skills, from other repositories
project-setup-info-local
Comprehensive setup steps to help the user create complete project structures in a VS Code workspace; this tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: user wants to create a new complete project from scratch; setting up entire project…
md-hive-sync
Munder Difflin hive sync — runs the start-of-task hive protocol steps: reads memory.md, checks inbox/ for new messages, and reminds you to record durable facts in memory.md and write coordination files before ending. Use when asked to "sync with the hive", "check my inbox", "hive status", or "hive sync". Proactively…
comet-native
A workflow for managing Native changes in Comet, where requirements, progress, and acceptance results are saved in project files. It uses the Comet command-line runtime to move through defined work stages.
comet-github-idea-to-issue
A workflow for turning a local idea, bug observation, or improvement proposal into a focused GitHub Issue draft. GitHub Issues are shared records for bugs, features, questions, and maintenance work.
generate-rfcs
Break the PRD into sequenced implementation RFCs under RFCs/ with an RFCS.md index, then cold-read each RFC for gaps.
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…