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 github-linkinggit 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/github-linking)<a href="https://agentmods.dev/skills/oortonaut/task-graph-mcp/github-linking"><img src="https://agentmods.dev/badge/skills/oortonaut/task-graph-mcp/github-linking/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/github-linking"><img src="https://agentmods.dev/badge/skills/oortonaut/task-graph-mcp/github-linking.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.00030 | $0.01912 |
| Opus 5.5 | $0.00012 | $0.00765 |
| Sonnet 5.5 | $0.00006 | $0.00382 |
| Haiku 4.5 | $0.00003 | $0.00191 |
Grade A, and why
github-linking 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub ↔ Task Graph Linking
Conventions and processes for maintaining bidirectional traceability between GitHub issues/PRs and task-graph tasks.
Prerequisite: Understand task-graph-basics for tool reference.
Overview
GitHub Task Graph
┌──────────────┐ attach ┌──────────────┐
│ Issue #42 │◄──────────────►│ brave-fox │
│ (bug report)│ github/issue │ (work task) │
└──────────────┘ └──────────────┘
│ │
│ PR #99 "Fixes #42" │ attach github/pr
▼ ▼
┌──────────────┐ attach ┌──────────────┐
│ PR #99 │◄──────────────►│ brave-fox │
│ (fix) │ github/pr │ (same task) │
└──────────────┘ └──────────────┘
Key idea: GitHub is the external record of truth. Task-graph is the internal coordination layer. Attachments bridge them.
Configuration
The project config (task-graph/config.yaml) defines these integration primitives:
Attachment Types
| Type | MIME | Mode | Purpose |
|---|---|---|---|
github/issue |
application/json |
replace | Link to a GitHub issue |
github/pr |
application/json |
replace | Link to a GitHub PR |
github/comment |
text/plain |
append | Notable comments from GitHub |
Dependency Type
| Type | Display | Blocks | Purpose |
|---|---|---|---|
tracks |
horizontal | none | Informational cross-reference to an external item |
Tags
| Tag | Category | Purpose |
|---|---|---|
github |
integration | Mark a task as linked to GitHub |
bug |
type | Mirror GitHub "bug" label |
enhancement |
type | Mirror GitHub "enhancement" label |
Process 1: Link Existing Issue to New Task
When a GitHub issue exists and you want to track work in task-graph:
# 1. Create the task
create(
title="Fix list_tasks ID truncation",
description="list_tasks truncates petname IDs to 8 chars in markdown output, making them unusable",
tags=["github", "bug"]
)
→ task_id (e.g. "brave-fox")
# 2. Attach the GitHub issue reference
attach(
agent=worker_id,
task="brave-fox",
type="github/issue",
content='{"repo": "Oortonaut/task-graph-mcp", "number": 1, "url": "https://github.com/Oortonaut/task-graph-mcp/issues/1"}'
)
# 3. (Optional) Add a comment on the GitHub issue pointing back
# gh issue comment 1 --body "Tracked in task-graph: brave-fox"
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 · 286 lines · 30 tokens per session scan A 503e3c141b83
github-linking is a skill published in the GitHub repository Oortonaut/task-graph-mcp (2 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,912 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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…