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 commands/dtannen/pm/task-syncgit clone --depth 1 https://github.com/dtannen/pmWhat 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.00011 | $0.01450 |
| Opus 5 | $0.00005 | $0.00725 |
| Sonnet 5 | $0.00002 | $0.00290 |
| Haiku 4.5 | $0.00001 | $0.00145 |
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 yesterday.
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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Task Progress to GitHub
Update GitHub issues with detailed progress from local task execution.
Usage
/pm:task-sync <task-file>
Example: /pm:task-sync 001-user-auth
Instructions
You are syncing progress for task: $ARGUMENTS
MCP Integration (preferred)
Reflect sync activity in MCP so task history remains canonical.
- Full name: mcp__project-manager-mcp__list_tasks — Resolve task by name
- Full name: mcp__project-manager-mcp__get_task_details — Retrieve current status/metadata
- Full name: mcp__project-manager-mcp__update_task — Append sync logs and GitHub issue linkage
Recommended flow:
- Resolve the task via
...__list_tasksand confirm with...__get_task_details. - After posting to GitHub, call
...__update_task(log_entry="Synced progress to GH issue #<n>", ra_metadata.github.issue_number, ra_metadata.github.url)to record the linkage in MCP. - Optionally reflect local progress percentages into
ra_metadata.progress.
1. Validate Task and Progress
- Check if
.pm/tasks/$ARGUMENTS.mdexists - Check if
.pm/tasks/$ARGUMENTS-progress.mdexists - Read current task status and progress details
- If no progress file: "⚠️ No progress tracked. Start task first: /pm:task-start $ARGUMENTS"
2. Gather Progress Information
From the task and progress files, collect:
- Current completion percentage
- Files created/modified
- Acceptance criteria status
- Test results
- Any issues or blockers encountered
- Time spent vs. estimated
3. Check GitHub Integration
Determine how to sync to GitHub:
Option A: GitHub CLI Available
# Check if gh CLI is available
if command -v gh &> /dev/null; then
echo "✅ GitHub CLI available"
else
echo "❌ GitHub CLI not found"
fi
Option B: Manual Issue Template
If no GitHub CLI, generate issue update template for manual posting.
4. Find or Create GitHub Issue
If using GitHub CLI:
# Look for existing issue with task title
gh issue list --search "in:title $ARGUMENTS" --json number,title,state
# If no issue exists, create one
if [ $? -ne 0 ]; then
gh issue create --title "Task: $ARGUMENTS" --body "$(cat issue_template)"
fi
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.
- yesterday First seen · 222 lines · 11 tokens per session scan A bf77c8a51e2d
task-sync is a command published in the GitHub repository dtannen/pm (0 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 1,450 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.