triage-github

triage-github is a command for coding agents from datacore-one/datacore. It costs 10 tokens per session (809 once invoked), scanned A, original, MIT.

Scan GitHub repos for activity, generate a summary, and create actionable GTD tasks.

Command

Install

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.

agentmods
npx agentmods add commands/datacore-one/datacore/triage-github
Clone the repo
git clone --depth 1 https://github.com/datacore-one/datacore

Wrote 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.

agentmods badge for triage-github

README.md
[![agentmods](https://agentmods.dev/badge/commands/datacore-one/datacore/triage-github.svg)](https://agentmods.dev/commands/datacore-one/datacore/triage-github)
Your own site
<a href="https://agentmods.dev/commands/datacore-one/datacore/triage-github"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/triage-github.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 809 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00809
Opus 5 $0.00005 $0.00404
Sonnet 5 $0.00002 $0.00162
Haiku 4.5 $0.00001 $0.00081

Measured today against content hash 33ef9c11869f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

triage-github 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 today.

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.

.datacore/modules/github/commands/triage-github.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/triage-github

Scan GitHub repos for activity, generate a summary, and create actionable GTD tasks.

Trigger

  • Standalone: /triage-github
  • Called by /today hook
  • Can be triggered by nightshift as a pre-processing step

Behavior

Execute these steps in order:

Step 1: Discover Repos

Run repo discovery (uses cache if < 7 days old):

python3 .datacore/modules/github/lib/repo_discovery.py \
  --data-dir ~/Data

Parse the JSON output to get the list of orgs and the org_to_spaces mapping.

Step 2: Scan GitHub

Run the full scan using discovered orgs:

python3 .datacore/modules/github/lib/github_scanner.py \
  --username plur9 \
  --orgs "<comma-separated orgs from step 1>" \
  --hours 24 \
  --cache .datacore/modules/github/data/scan_cache.json \
  --format json

Step 3: Create Tasks

If auto_task_create is enabled (default: true), create tasks from actionable items:

python3 .datacore/modules/github/lib/task_creator.py \
  --scan-file .datacore/modules/github/data/scan_cache.json \
  --repos-file .datacore/modules/github/data/repos.json \
  --data-dir ~/Data

Step 4: Generate Summary

Use the scan results to produce a markdown summary. Call format_summary() from github_scanner.py or generate inline using this template:

YOUR ITEMS section (full structured detail for mentions + authored issues):

### GitHub: Your Items

**@plur9 mentions:**
- owner/repo#N — "Issue title"
  State: open | [View](url)

**Your issues with new activity:**
- owner/repo#N — "Issue title"
  Latest by @commenter: comment snippet...
  [View](url)

OTHER ACTIVITY section (compact counts per org):

### GitHub: Org Activity

| Org | New Issues | Closed | PRs Merged |
|-----|-----------|--------|------------|
| org-name (space) | N | N | N |

TASKS CREATED section (audit trail):

### GitHub: Tasks Created

- N new tasks created in next_actions.org
- N items skipped (already tracked)
- Tasks tagged :AI:github: for nightshift processing

Read the full file on GitHub · 126 lines

Changes

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.

  1. today First seen · 126 lines · 10 tokens per session scan A 33ef9c11869f

Subscribe to this mod's changes

triage-github is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 809 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-09-03.