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 ryanzhao1011/workframe --skill task-managementgit clone --depth 1 https://github.com/ryanzhao1011/workframeWrote 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/ryanzhao1011/workframe/task-management)<a href="https://agentmods.dev/skills/ryanzhao1011/workframe/task-management"><img src="https://agentmods.dev/badge/skills/ryanzhao1011/workframe/task-management/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/ryanzhao1011/workframe/task-management"><img src="https://agentmods.dev/badge/skills/ryanzhao1011/workframe/task-management.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.00131 | $0.04936 |
| Opus 5.5 | $0.00052 | $0.01974 |
| Sonnet 5.5 | $0.00026 | $0.00987 |
| Haiku 4.5 | $0.00013 | $0.00494 |
Grade A, and why
task-management 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 23d 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.
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
任务管理技能
board.yaml 格式规范
# projects/board.yaml
summary:
total: 0
pending: 0
in_progress: 0
pending_qa: 0
completed: 0
blocked: 0
cancelled: 0
last_updated: "YYYY-MM-DD"
tasks:
- id: "TASK-001"
title: "任务标题"
description: "任务描述"
status: pending # pending | in_progress | pending_qa | completed | blocked | cancelled
priority: P1 # P0 | P1 | P2
assigned_to: dev # pm | dev | qa | prompt-eng
created_at: "YYYY-MM-DD"
updated_at: "YYYY-MM-DD"
deadline: null # "YYYY-MM-DD" 可选；有截止要求才填。heartbeat-check.py 会扫此字段判逾期
depends_on: [] # 依赖的任务 ID 列表
tags: [] # 标签（合法值见下方约定）
estimate_hours: 4 # 预估工时（小时）
notes: "" # 备注
# ── modules/ 体系叠加字段 ──
# module: profile/edit # ★ 二段式 basic/sub；modules/ 体系下必填
# req_slug: avatar-cropper # 可选；需求级任务用，对应 modules/<basic>/<sub>/requirements/<req_slug>/
# sub_req_slug: main # 与 req_slug 同进同出；main 也要显式写
# # （缺省按 main 解释仅对**存量**条目成立）
# affected_modules: [] # 可选；横切多模块任务用二段式数组
# ── 可选生命周期字段（按事件触发写入）─────────────────────
# completed_at: "YYYY-MM-DD" # status 改为 completed 时填写
# actual_output: "" # completed 时补充实际产出描述
# blocked_reason: "" # status 改为 blocked 时必填
# cancelled_at: "YYYY-MM-DD" # status 改为 cancelled 时填写
# cancel_reason: "" # cancelled 时必填
modules/ 体系字段
modules/ 体系下，task 字段叠加 modules 归属：
| 字段 | 取值 | 必填条件 |
|---|---|---|
module |
二段式 <basic>/<sub>，如 profile/edit |
modules/ 体系下必填（与 issue 字段策略一致） |
req_slug |
父需求 slug，如 avatar-cropper |
需求级任务必填（document-norms §2.6 引用契约）；维护 / 看板 / 记忆整理这类不挂需求的任务留空 |
sub_req_slug |
子需求 slug，如 main 或 phase-1 |
与 req_slug 同进同出——填了 req_slug 就必须填它（main 也显式写）。只有存量条目缺它时才按 main 解释，那是兼容条款不是写法（document-norms §2.6） |
affected_modules |
二段式数组 [a/b, c/d] |
横切多模块任务可选 |
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.
- 23d ago Changed · +53 lines · +111 tokens per session scan B → A f80130cc50c6
- 1mo ago First seen · 199 lines · 20 tokens per session scan B 00e8440dbba4
task-management is a skill published in the GitHub repository ryanzhao1011/workframe (7 stars, last pushed 24d ago), licensed MIT. It adds 131 tokens to every session and 4,936 once invoked, about $0.0005 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-31.
Other skills, from other repositories
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
write-prd
Write PRD — Product Requirements Documents with structured 8-section templates, user stories, acceptance criteria, and value proposition validation. Use when writing PRDs, defining product requirements, creating user stories with INVEST criteria, or building go/no-go decision frameworks.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
expo-eas-submit
App Store Connect and Google Play Console upload flow with EAS Submit, metadata, build-artifact selection, review notes, and phased release. Triggers on eas submit, app store connect, google play, asc api key, service account, metadata, screenshot, phased release, review notes, testflight, internal testing, production…
vault-tasks
A set of rules for managing tasks as tagged checkbox lines inside Obsidian notes with the Tasks plugin. It covers labels, work types, priorities, dates, statuses, inbox capture, and weekly review.