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/atebites-hub/pjtemplate/taskboard-workflownpx skills add atebites-hub/PJTemplate --skill taskboard-workflowgit clone --depth 1 https://github.com/atebites-hub/PJTemplateWrote 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/atebites-hub/pjtemplate/taskboard-workflow)<a href="https://agentmods.dev/skills/atebites-hub/pjtemplate/taskboard-workflow"><img src="https://agentmods.dev/badge/skills/atebites-hub/pjtemplate/taskboard-workflow.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.00054 | $0.00613 |
| Opus 5 | $0.00027 | $0.00307 |
| Sonnet 5 | $0.00011 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
taskboard-workflow 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 3d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taskboard workflow
Coordination board for this repo. Not a replacement for task memory (C3) or git pre-commit compliance (C1/C3).
Data mapping
| Taskboard | This repo |
|---|---|
| Project | One per clone (project_slug in config/setup.toml, else the repo name) |
| Ticket | One sprint item in docs/agents/implementation_plan.md |
| Subtask | Optional checklist; not a memory file |
| SQLite | Always .taskboard/taskboard.db in the project root |
Never use the default ~/Library/Application Support/taskboard/taskboard.db
(Linux: ~/.config/taskboard/taskboard.db). Every CLI call takes --db first:
taskboard --db "${CLAUDE_PROJECT_DIR:-.}/.taskboard/taskboard.db" <subcommand>
The Claude plugin MCP server already passes that --db. Cursor/Codex must pass
it on every CLI invocation.
Link to C3 memory
After create_ticket / taskboard ticket create, write this line on the
matching docs/memories/*.md file:
Taskboard: <ticket-uuid>
Use the UUID (id in MCP / the parenthetical id in CLI output), not the
display key (AUTH-1). ticket move looks up UUID only.
Hooks only auto-move tickets that have this line. No ID → no auto-move.
Memories keep Context / Evaluation / Key Challenges. Do not copy workflow
steps onto the board.
When to create tickets
After the human approves the plan, create or claim tickets for current sprint items. Do not file one ticket per memory file. Do not spawn agents from the Taskboard UI.
Statuses: todo | in_progress | done.
When the memory state: becomes completed, move the linked ticket to done
(the Stop/commit hook does this if the CLI is on PATH; do it yourself if not).
MCP vs CLI
Prefer MCP tools when they are connected (create_project, create_ticket,
move_ticket, list_tickets, get_board, …). Otherwise CLI with --db.
Install the binary (not vendored):
brew tap tcarac/taskboard && brew install taskboard
# or: clone atebites-hub/taskboard && make build
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.
- 3d ago First seen · 74 lines · 54 tokens per session scan A 54d024675f40
taskboard-workflow is a skill published in the GitHub repository atebites-hub/PJTemplate (2 stars, last pushed 11d ago), licensed MIT. It adds 54 tokens to every session and 613 once invoked, about $0.0003 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-31.
Other skills, from other repositories
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
manage-project
Research project management for medical manuscripts. Scaffold project structure, track writing progress across phases, maintain project memory files, generate submission checklists and backwards timelines. Commands: init, status, sync-memory, checklist, timeline.
td-task-management
Task management for AI agents across context windows. Use when agents need to track work, log progress, hand off state, and maintain context across sessions. Includes workflows for single-issue focus, multi-issue work sessions, and structured handoffs. Essential for AI-assisted development where context windows reset…
harness-step3-session-management
Harness Engineering 第二阶段：建立跨 session 状态管理，解决 agent 每次对话失忆的问题。 创建 tasks.json（任务清单）、progress.md（进度记录）、init.sh（环境初始化脚本）三个文件。 当用户说"建立任务管理"、"让 agent 记住进度"、"创建 tasks.json"、"跨 session 保持状态"、 "agent 每次都不记得上次做了什么"、"建立 progress 文件"、"初始化状态管理"时，立即使用此 skill。 前置条件：harness-step1 和 harness-step2 已完成（项目有 AGENTS.md 和 docs/ 知识库）。.
harness-design
Design and build multi-agent harness architectures for long-running AI application development. GAN-inspired Generator-Evaluator pattern, Sprint Contract negotiation, context management, quality criteria calibration. Based on Anthropic Engineering patterns. Use when: "build a harness", "multi-agent architecture"…
okf-pro
Operating rules for the .okf/ knowledge bundle — filing new concepts, the board, the journal, the daily snapshot, closing work, source attribution, and the generated/verified attestation policy. Use before reading from or writing anything into .okf/.