Borrowing it
Nothing to install: this file belongs to nicepkg/vsync. 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/nicepkg/vsync/main/.claude/commands/do-task.mdgit clone --depth 1 https://github.com/nicepkg/vsyncWrote 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/commands/nicepkg/vsync/do-task)<a href="https://agentmods.dev/commands/nicepkg/vsync/do-task"><img src="https://agentmods.dev/badge/commands/nicepkg/vsync/do-task/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/commands/nicepkg/vsync/do-task"><img src="https://agentmods.dev/badge/commands/nicepkg/vsync/do-task.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.00010 | $0.02777 |
| Opus 5.5 | $0.00004 | $0.01111 |
| Sonnet 5.5 | $0.00002 | $0.00555 |
| Haiku 4.5 | $0.00001 | $0.00278 |
Grade A, and why
do-task 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.
How it starts
The opening of the file, as written. The whole thing — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Do Task - vsync
Execute development tasks from TASKS.md following vsync project specifications and TDD workflow.
Current Context
- Current branch: !
git branch --show-current - Git status: !
git status --short | head -20
Phase Overview
!grep -E "^## Phase [0-9]:|^\*\*Current Status\*\*:" TASKS.md | head -20
Instructions
1. Task Selection
If $ARGUMENTS is provided:
- If it's a phase-task reference (e.g.,
Phase 1.1,Phase 2.3), work on that specific task - If it's
next, pick the next uncompleted task[ ]in the current phase
If no argument, show current phase and ask which task to work on.
2. Before Starting - CRITICAL READS
MUST READ in this order:
| Document | Purpose | Time | Critical Sections |
|---|---|---|---|
| TASKS.md | Current phase & task details | 2 min | Current phase section |
| CLAUDE.md | AI-specific rules & workflows | 5 min | Critical Rules, Config Formats, TDD |
| docs/prd.md | Detailed specifications | 10 min | Section 2 (Config Formats), relevant sections |
| docs/config.md | Project configuration values | 1 min | All fields |
3. Task Execution Workflow (TDD)
1. Read task from TASKS.md
2. Check phase dependencies (previous phases must be complete)
3. Read relevant documentation sections
4. **WRITE TESTS FIRST** (cli/test/[module].test.ts)
- Use vitest + mock-fs
- Cover all edge cases
5. Implement code (src/[module].ts)
- Follow patterns in CLAUDE.md
- Match config formats EXACTLY (see PRD Section 2)
6. Run tests: pnpm test
7. Verify: pnpm typecheck && pnpm lint
8. Mark task [x] in TASKS.md
9. Update phase status if phase complete
10. Commit with Angular convention
4. Critical Implementation Rules
Config Format Precision (see PRD Section 2.2):
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 · 356 lines · 10 tokens per session scan A b9b88e62afc0
do-task is a command published in the GitHub repository nicepkg/vsync (61 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 2,777 once invoked, about $0.0000 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 commands, from other repositories
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
handoff
Write a session handoff document for continuity.
update-docs
Scan recently modified files and update the matching documentation.
amby.implement
Execute the task list, checking off tasks and updating story status as you go.
amby.analyze
Cross-check spec, plan, and tasks for coverage, consistency, and dependency-graph health.