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-repairgit 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-repair)<a href="https://agentmods.dev/skills/oortonaut/task-graph-mcp/task-graph-repair"><img src="https://agentmods.dev/badge/skills/oortonaut/task-graph-mcp/task-graph-repair/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-repair"><img src="https://agentmods.dev/badge/skills/oortonaut/task-graph-mcp/task-graph-repair.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.00033 | $0.02084 |
| Opus 5.5 | $0.00013 | $0.00834 |
| Sonnet 5.5 | $0.00007 | $0.00417 |
| Haiku 4.5 | $0.00003 | $0.00208 |
Grade A, and why
task-graph-repair 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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Graph Repair
Diagnose and fix common issues: orphaned tasks, broken dependencies, stale claims, disconnected agents, and data inconsistencies.
Prerequisite: Understand task-graph-basics for tool reference.
Quick Start
# 1. Connect with repair capabilities
connect(name="repair-agent", tags=["repair", "admin"])
→ agent_id
# 2. Run diagnostics
list_tasks(format="markdown") # Overview
list_tasks(blocked=true) # Blocked tasks
list_agents(format="markdown") # Agent status
# 3. Fix issues as discovered
# (See specific repair procedures below)
Diagnostic Checklist
Run these queries to identify issues:
| Query | Looking For |
|---|---|
list_tasks(blocked=true) |
Tasks stuck on deps |
list_tasks(status="working") |
Potentially stale work |
list_agents() |
Disconnected/stale agents |
list_marks() |
Abandoned file marks |
list_tasks(parent="null") |
Unexpected root tasks |
Issue: Orphaned Tasks
Symptoms: Tasks with no parent that shouldn't be root tasks.
Diagnosis:
# Find all root tasks
list_tasks(parent="null")
# Identify which are intentional vs orphaned
# Orphaned = was child, parent deleted without cascade
Repair Options:
# Option A: Re-parent to correct parent
update(agent=agent_id, task=orphan_id, parent=correct_parent_id)
# Option B: Delete if no longer needed
delete(task=orphan_id, cascade=true)
# Option C: Make intentional root
# (No action needed, just document)
Issue: Broken Dependencies
Symptoms: Task blocked by non-existent task, or circular dependency.
Diagnosis:
# Find blocked tasks
list_tasks(blocked=true)
# For each, check blockers exist
get(task=blocked_task_id) # Look at blockedBy field
# Try to fetch each blocker
get(task=blocker_id) # Will fail if deleted
Repair:
# Remove reference to deleted blocker
unblock(blocker=deleted_task_id, blocked=stuck_task_id)
# For circular deps (rare, should be rejected):
# Break the cycle by removing one edge
unblock(blocker=task_a, blocked=task_b)
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 · 382 lines · 33 tokens per session scan A 8149df61cee0
task-graph-repair is a skill published in the GitHub repository Oortonaut/task-graph-mcp (2 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 2,084 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.