task-sync

A command for collecting tasks from project files into dashboards/TASKS.md and, with the push option, sending checkbox changes back to those source files.

In plain words
What is it for?
Use it to aggregate tasks with no argument or pull, or synchronize dashboard changes back to project files with push.
Why use it?
It keeps tasks visible in one dashboard while preserving their connection to the projects where they belong.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/superuser-pal/awesome-second-brain/task-sync
Clone the repo
git clone --depth 1 https://github.com/superuser-pal/awesome-second-brain

Made for: Claude Code.

Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 125 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00125
Opus 5 $0.00018 $0.00063
Sonnet 5 $0.00007 $0.00025
Haiku 4.5 $0.00004 $0.00013

Measured 2d ago against content hash e67c2db8b25f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

task-sync 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 2d 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.

.claude/commands/manage/task-sync.md · 11 lines

What it actually says

Sync tasks using the project-management skill.

  • No argument or pull: run the pull-tasks workflow — scan all domain projects and work/01_PROJECTS/, output to dashboards/TASKS.md.
  • push: run the update-tasks workflow — push checkbox changes from dashboards/TASKS.md back to source project files.

$ARGUMENTS

Changes

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.

  1. 2d ago First seen · 11 lines · 37 tokens per session scan A e67c2db8b25f

Subscribe to this mod's changes

task-sync is a command published in the GitHub repository superuser-pal/awesome-second-brain (14 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 125 once invoked, about $0.0002 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.