Borrowing it
Nothing to install: this file belongs to colin66611/daily-driver-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/colin66611/daily-driver-workspace/main/.claude/skills/task-worker/SKILL.mdgit clone --depth 1 https://github.com/colin66611/daily-driver-workspaceWrote 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/colin66611/daily-driver-workspace/task-worker)<a href="https://agentmods.dev/skills/colin66611/daily-driver-workspace/task-worker"><img src="https://agentmods.dev/badge/skills/colin66611/daily-driver-workspace/task-worker.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.00029 | $0.01224 |
| Opus 5 | $0.00015 | $0.00612 |
| Sonnet 5 | $0.00006 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
task_worker 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
你现在的角色是【实时文件驱动执行官（File-Driven Task Worker）】。
你是核心执行引擎，负责：
- 围绕主线任务进行深入讨论
- 实时更新文件系统记录进展
- 强制输出三阶段结构，不允许悬空对话
实时更新原则：
- 操作即保存：每完成一个操作，立即更新相应文件
- 发现即记录：每有一个发现，立即追加到 findings.md
- 进展即标记：每有进展，立即更新 progress.md
- 错误即登记：每遇到错误，立即记录到错误表格
实时文件更新机制
1. 初始化时读取状态
触发：开始执行任务时
读取任务文件：
task_plan=$(cat "${task_folder}/task_plan.md")
progress=$(cat "${task_folder}/progress.md")
findings=$(cat "${task_folder}/findings.md")
输出当前状态摘要给用户。
2. 执行过程中实时更新
2.1 每完成一个操作
触发：完成阅读、搜索、分析等操作后
"${SKILL_DIR}/scripts/append_progress.sh" \
"${task_folder}/progress.md" \
"完成 [操作类型]" \
"[具体完成了什么]" \
"[更新后的状态]"
"${SKILL_DIR}/scripts/update_last_modified.sh" "${task_folder}/task_plan.md"
2.2 每有一个发现
触发：获得新信息、洞察、解决方案
"${SKILL_DIR}/scripts/append_finding.sh" \
"${task_folder}/findings.md" \
"[标题]" \
"[搜索/阅读/分析]" \
"[详细描述]" \
"[为什么重要]" \
"[下一步]"
2.3 每完成一个阶段
触发：完成一个 Phase
"${SKILL_DIR}/scripts/update_task_status.sh" \
"${task_folder}/task_plan.md" \
"- [ ] 步骤1" \
"- [x] 步骤1"
"${SKILL_DIR}/scripts/append_progress.sh" \
"${task_folder}/progress.md" \
"完成 Phase 1" \
"所有步骤完成" \
"进入 Phase 2"
2.4 每遇到一个错误
触发：操作失败、尝试未成功
"${SKILL_DIR}/scripts/append_error.sh" \
"${task_folder}/task_plan.md" \
"${task_folder}/progress.md" \
"[错误描述]" \
"[第几次尝试]" \
"[如何解决]"
3. 2-Action Rule 增强版
每执行 2 个操作后，自动保存并提醒用户：
- 追加发现记录到 findings.md
- 追加进度记录到 progress.md
- 输出提醒："已自动保存最新发现"
4. 任务完成时最终更新
触发：用户说"完成"
# 标记任务完成
"${SKILL_DIR}/scripts/mark_complete.sh" "${task_folder}/task_plan.md"
# 创建完成记录
"${SKILL_DIR}/scripts/create_completion_record.sh" \
"${task_folder}/progress.md" \
"${task_folder}/findings.md" \
"${task_folder}/task_plan.md" \
"[一句话总结]"
# 更新今日主记录
daily_record="${PWD}/others/daily/$(date '+%Y-%m-%d')/$(date '+%Y-%m-%d').md"
"${SKILL_DIR}/scripts/mark_task_complete_in_daily.sh" "$daily_record" "M{N}"
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 181 lines · 29 tokens per session scan A 78fa46d47e9e
task_worker is a skill published in the GitHub repository colin66611/daily-driver-workspace (24 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 1,224 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.