Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/datacore-one/datacorenpx agentmods add commands/datacore-one/datacore/triage-githubWrote 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/commands/datacore-one/datacore/triage-github)<a href="https://agentmods.dev/commands/datacore-one/datacore/triage-github"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/triage-github/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/commands/datacore-one/datacore/triage-github"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/triage-github.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.00010 | $0.00829 |
| Opus 5.5 | $0.00004 | $0.00332 |
| Sonnet 5.5 | $0.00002 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
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 yesterday.
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 — 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
/todayhook - 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 <username from module settings> \
--orgs "<comma-separated orgs from step 1>" \
--hours 24 \
--cache 0-personal/.datacore/module-data/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 0-personal/.datacore/module-data/github/data/scan_cache.json \
--repos-file 0-personal/.datacore/module-data/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
**@<username> 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
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.
- yesterday Changed ce87956ec240
- 20d ago Changed 2d28f2c72493
- 1mo ago First seen · 126 lines · 10 tokens per session scan A 33ef9c11869f
triage-github is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 829 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
run-task
Run pending steps, then aftertask finalization; does not close the task.
finish-task
Deprecated alias for close-task.
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
company-repo
Gestionar el repositorio Company Savia: crear, conectar, estado, sincronizar. El repositorio compartido de la empresa para conocimiento, mensajería y estado.
iterate
Execute a single Ralph loop iteration - complete one work unit from tasks.md with proper commits and progress tracking.