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/oortonaut/task-graph-mcp/task-graph-migrationnpx skills add Oortonaut/task-graph-mcp --skill task-graph-migrationgit clone --depth 1 https://github.com/Oortonaut/task-graph-mcpWhat 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.00034 | $0.02147 |
| Opus 5 | $0.00017 | $0.01073 |
| Sonnet 5 | $0.00007 | $0.00429 |
| Haiku 4.5 | $0.00003 | $0.00215 |
Grade A, and why
task-graph-migration 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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Graph Migration
Import tasks from external systems: GitHub Issues, Linear, Jira, markdown TODOs, and plain text task lists.
Prerequisite: Understand task-graph-basics for tool reference.
Quick Start
# 1. Connect
connect(name="migrator", tags=["migration"])
→ agent_id
# 2. Create root task for migration batch
create(title="Migrated: {source}")
→ root_id
# 3. For each source task, create in task-graph
create(parent=root_id, title="...", description="...")
# 4. Preserve relationships
block(blocker=task_a, blocked=task_b)
Source Formats
GitHub Issues
Source: gh issue list --json number,title,body,state,labels
Mapping:
issue.title → task.title
issue.body → task.description
issue.state → task.status (open→pending, closed→completed)
issue.labels → task.agent_tags_all
issue.milestone → parent task
Linear
Source: Linear API or export
Mapping:
issue.title → task.title
issue.description → task.description
issue.state → task.status
issue.priority → task.priority (1→critical, 2→high, 3→medium, 4→low)
issue.estimate → task.points
issue.parent → parent relationship
issue.blockedBy → block() dependencies
Jira
Source: Jira API or CSV export
Mapping:
issue.summary → task.title
issue.description → task.description
issue.status → task.status
issue.priority → task.priority
issue.storyPoints → task.points
issue.epic → parent task
issue.links → block() dependencies
Markdown TODOs
Source: Any markdown file with task lists
Pattern:
- [ ] Task title
- [x] Completed task
- [ ] Task with @tag
Mapping:
[ ] → status: pending
[x] → status: completed
@tag → agent_tags_all
indent level → parent/child hierarchy
Plain Text
Source: Numbered or bulleted lists
Pattern:
1. First task
2. Second task (depends on 1)
3. Third task
Mapping:
Sequential numbers → sibling_type: "follows" (top-level param)
Parallel items → sibling_type: null (or omit)
Indentation → hierarchy
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 · 385 lines · 34 tokens per session scan A f51a3cd7d2fb
task-graph-migration is a skill published in the GitHub repository Oortonaut/task-graph-mcp (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,147 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…