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-statusgit 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-status)<a href="https://agentmods.dev/skills/stanshy/agenthub/task-status"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/task-status/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-status"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/task-status.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.00015 | $0.00746 |
| Opus 5.5 | $0.00006 | $0.00298 |
| Sonnet 5.5 | $0.00003 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
task-status 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
任務狀態更新
任意角色更新任務狀態（中間狀態），自動追加事件紀錄。
使用方式
/task-status {task-id} {new-status} {備註（可選）}
範例
/task-status T3 in_progress L1 分派給 backend-architect 執行
/task-status T5 blocked 等待 T4 完成
/task-status T7 assigned 已分派給 frontend-developer
合法狀態（系統解析依賴，務必使用英文小寫值）
| 狀態值 | 說明 | 系統對應 |
|---|---|---|
created |
已建立，尚未分配 | created |
assigned |
已分配，尚未開始 | assigned |
in_progress |
進行中 | in_progress |
in_review |
審查中 | in_review |
blocked |
被阻塞 | blocked |
done |
完成（建議改用 /task-done） | done |
rejected |
被退回 | rejected |
禁止使用中文狀態值（如「進行中」）或自定義值。 系統解析器
normalizeStatus()可容忍✅ 完成/🔄 進行中等 emoji 前綴格式， 但.tasks/檔案的狀態欄位必須使用純英文值。
執行步驟
-
解析參數：從
$ARGUMENTS提取 task-id、new-status、備註 -
找到任務檔案（支援 Sprint 子目錄）： 使用 Glob tool 搜尋
.tasks/**/$0-*.md，若無結果再搜尋.tasks/**/$0.md。 取得檔案路徑後用 Read tool 讀取內容。
任務檔案可能在
.tasks/sprint-{N}/T3-xxx.md，不再只在.tasks/根目錄。
-
取得真實時間（必要，不可跳過）： !
node -e "console.log(new Date().toISOString())"⚠️ 禁止自行編造時間。Agent 不知道真實時間，必須透過上述指令取得。將輸出存為變數
$NOW供後續步驟使用。 -
更新狀態欄位：將
| 狀態 | xxx |修改為| 狀態 | {new-status} | -
事件紀錄（必要，不可跳過）：在
## 事件紀錄區塊底部 append：
### $NOW — 狀態變更 → {new-status}
{備註}
- 完成提示：
- 如果 new-status 是
done，提示用戶改用/task-done（因為 done 需要同步更新 dev-plan 第 10 節） - 否則輸出確認訊息：
✅ {task-id} 狀態已更新為 {new-status}
- 如果 new-status 是
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 · 64 lines · 15 tokens per session scan A 42989b3c7641
task-status is a skill published in the GitHub repository Stanshy/AgentHub (204 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 746 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.…