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 skills add Oortonaut/task-graph-mcp --skill task-graph-reportinggit clone --depth 1 https://github.com/Oortonaut/task-graph-mcpWrote 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/oortonaut/task-graph-mcp/task-graph-reporting)<a href="https://agentmods.dev/skills/oortonaut/task-graph-mcp/task-graph-reporting"><img src="https://agentmods.dev/badge/skills/oortonaut/task-graph-mcp/task-graph-reporting/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/skills/oortonaut/task-graph-mcp/task-graph-reporting"><img src="https://agentmods.dev/badge/skills/oortonaut/task-graph-mcp/task-graph-reporting.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.00029 | $0.02002 |
| Opus 5.5 | $0.00012 | $0.00801 |
| Sonnet 5.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 2mo 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.
- 2mo 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 7mo 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.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.