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-reportingnpx skills add Oortonaut/task-graph-mcp --skill task-graph-reportinggit 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.00029 | $0.02002 |
| Opus 5 | $0.00015 | $0.01001 |
| Sonnet 5 | $0.00006 | $0.00400 |
| Haiku 4.5 | $0.00003 | $0.00200 |
Grade A, and why
task-graph-reporting 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Graph Reporting
Generate progress reports, analyze metrics, track costs and velocity across task-graph projects.
Prerequisite: Understand task-graph-basics for tool reference.
Quick Start
# Connect (reporting doesn't need special tags)
connect(name="reporter", tags=["reporting"])
→ agent_id
# Get project overview
list_tasks(format="markdown")
# Analyze specific task tree
get(task=root_task_id, children=true, format="markdown")
# Check agent activity
list_agents(format="markdown")
Report Types
1. Status Report
Quick overview of project state:
┌─────────────────────────────────────────┐
│ STATUS REPORT │
├─────────────────────────────────────────┤
│ Query: list_tasks(format="markdown") │
│ │
│ Metrics to extract: │
│ • Total tasks by status │
│ • Blocked tasks and blockers │
│ • Active agents and their tasks │
│ • Ready tasks (available work) │
└─────────────────────────────────────────┘
2. Progress Report
Track completion over time:
┌─────────────────────────────────────────┐
│ PROGRESS REPORT │
├─────────────────────────────────────────┤
│ Queries: │
│ • list_tasks(status="completed") │
│ • list_tasks(status="working") │
│ • list_tasks(status="pending") │
│ │
│ Calculate: │
│ • Completion rate (completed/total) │
│ • Points completed vs remaining │
│ • Time actual vs estimated │
└─────────────────────────────────────────┘
3. Cost Report
Analyze resource consumption:
┌─────────────────────────────────────────┐
│ COST REPORT │
├─────────────────────────────────────────┤
│ Query: get(task=root, children=true) │
│ │
│ Aggregate across tasks: │
│ • tokens_in, tokens_out, tokens_cached │
│ • tokens_thinking, tokens_image/audio │
│ • cost_usd total and per-task │
└─────────────────────────────────────────┘
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 · 384 lines · 29 tokens per session scan A 43dd3fa1b6ce
task-graph-reporting is a skill published in the GitHub repository Oortonaut/task-graph-mcp (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 2,002 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 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…