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/michael-harris/devteam/merge-tracksnpx skills add michael-harris/devteam --skill merge-tracksgit clone --depth 1 https://github.com/michael-harris/devteamWrote 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/michael-harris/devteam/merge-tracks)<a href="https://agentmods.dev/skills/michael-harris/devteam/merge-tracks"><img src="https://agentmods.dev/badge/skills/michael-harris/devteam/merge-tracks.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.00028 | $0.02603 |
| Opus 5 | $0.00014 | $0.01301 |
| Sonnet 5 | $0.00006 | $0.00521 |
| Haiku 4.5 | $0.00003 | $0.00260 |
Grade A, and why
merge-tracks 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 4d 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Current session: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_current_session 2>/dev/null || echo "No active session"
Active sprint: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_kv_state "active_sprint" 2>/dev/null || echo "None"
Failure count: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_kv_state "consecutive_failures" 2>/dev/null || echo "0"
Merge Tracks Command
Debug/Expert Command - Manually merge parallel development tracks.
Note: This command is rarely needed. Track merging happens automatically when all tracks complete via
/devteam:implement. Use this only if automatic merge failed or you need manual control over the merge process.
You are orchestrating the parallel development tracks merging phase to combine all completed tracks back into the main branch.
Command Usage
/devteam:merge-tracks # Merge all tracks, create PR, cleanup worktrees (default)
/devteam:merge-tracks --manual-merge # Merge all tracks, skip PR, cleanup worktrees
/devteam:merge-tracks --keep-worktrees # Merge, create PR, keep worktrees
/devteam:merge-tracks --delete-branches # Merge, create PR, cleanup worktrees & branches
/devteam:merge-tracks --dry-run # Show what would be merged without doing it
Flags:
--manual-merge: Skip automatic PR creation after merge, allow manual PR creation--keep-worktrees: Keep worktrees after merge (default: delete)--delete-branches: Delete track branches after merge (default: keep)--dry-run: Preview merge plan without executing
Prerequisites
This command only works for projects planned with git worktrees (--use-worktrees flag).
Pre-flight checks:
- SQLite state database must exist with worktree mode enabled
- All tracks must be complete (all sprints in all tracks marked "completed")
- No uncommitted changes in any worktree
- All worktrees should have pushed to remote (optional but recommended)
Your Process
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.
- 4d ago First seen · 333 lines · 0 tokens per session scan A 95aeaaf8fa2e
merge-tracks is a skill published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 2,603 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
knowledge-gaps
This skill should be used when the user asks about 'knowledge gaps', 'tool coverage', 'undocumented dependencies', 'undocumented tools', 'concept gaps', 'installed plugins', 'plugin coverage', 'undocumented skills', 'globally installed plugins/skills', 'what is installed on this machine', 'stale/outdated/drifted…
people-intel
This skill should be used when the user asks to 'research person', 'person intel', 'people intel', 'who is [person]', 'who created [project]', 'who maintains [package]', 'add person to knowledge graph', 'enrich person note', 'update person note', 'document [person]', 'create person note for [name]'. Researches a…
schema-evolve
This skill should be used when the user asks about 'schema drift', 'schema evolution', 'evolve schema', 'schema sync', 'sync schemas', 'update schema fields', 'schema field frequency', 'missing schema fields', 'unused schema fields', 'schema proposal', 'schema cardinality', 'check schema', 'schema audit', 'schema…
knowledge-maintain
This skill should be used when the user asks to fix, repair, or tidy one or more SPECIFIC named notes — 'fix these notes', 'fix the issues in [note]', 'add the missing relations to [note]', 'tidy up [note]', 'fix orphan [note]', 'apply the gardener findings for [note]'. Applies structural fixes (missing sections…
raindrop-triage
This skill should be used when the user asks to 'triage unsorted bookmarks', 'clean up raindrop inbox', 'sort unsorted', 'organize bookmarks', 'raindrop triage', 'process bookmark backlog', 'promote triaged bookmarks', 'classify triaged', 'raindrop cleanup', 'deduplicate bookmarks', 'find duplicate bookmarks', 'tag…
knowledge-garden
This skill should be used when the user asks to audit, health-check, or structurally validate one or more SPECIFIC named notes or a bounded topic cluster — 'audit these notes', 'check this note for orphans or broken links', 'fourth-wall check on [note]', 'validate the structure of [note]', 'spot-check [note]'. Runs a…