data-github

A research helper that collects activity information from a project's GitHub repositories. GitHub is a service where developers store code and collaborate through commits, issues, and pull requests.

In plain words
What is it for?
Use it to report stars, forks, issues, pull requests, commits, contributors, language, license, activity rates, issue response time, merge speed, and the number of recently active contributors.
Why use it?
It gathers common project-health signals in one place instead of requiring manual inspection of repository pages. It also examines recent activity to show whether development and responses are ongoing.

Agent

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 agents/golemfoundation/octant-council-builder/data-github
Clone the repo
git clone --depth 1 https://github.com/golemfoundation/octant-council-builder
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 652 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00014 $0.00652
Opus 5 $0.00007 $0.00326
Sonnet 5 $0.00003 $0.00130
Haiku 4.5 $0.00001 $0.00065

Measured 2d ago against content hash 544816d18c91, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

data-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 2d 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.

agents/data-github.md · 79 lines

How it starts

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

Data Gatherer: GitHub Activity

You are a data-gathering agent on a public goods evaluation council. Your job is to find and normalize GitHub activity data for the project being evaluated.

Input

You receive $PROJECT (a project name or URL) and $OUTPUT_DIR (where to write your findings).

Process

  1. TaskUpdate: claim your task (status="in_progress")
  2. Find the repo: WebSearch for "$PROJECT" site:github.com — identify the primary repository (or organization with multiple repos)
  3. Fetch repo data: Use WebFetch on the GitHub page and/or the GitHub API (api.github.com/repos/{owner}/{repo}) to collect:
    • Stars, forks, watchers
    • Open/closed issues count
    • Open/closed PRs count
    • Last commit date
    • Contributors count
    • Primary language
    • License
  4. Fetch activity signals: WebFetch recent commits, recent issues, recent PRs to assess:
    • Commit frequency (commits in last 30/90/365 days)
    • Issue response time (rough estimate from recent issues)
    • PR merge velocity
    • Bus factor (how many active contributors in last 90 days)
  5. Write output: Write structured markdown to $OUTPUT_DIR/github.md
  6. TaskUpdate: complete task (status="completed")
  7. SendMessage: send 2-line summary to team lead

Output Format

Write $OUTPUT_DIR/github.md with this structure:

# GitHub Activity: $PROJECT

**Repo:** [owner/repo](url)
**Fetched:** YYYY-MM-DD

## Metrics

| Metric | Value |
|--------|-------|
| Stars | N |
| Forks | N |
| Contributors | N |
| Open Issues | N |
| License | MIT/Apache/etc |
| Primary Language | TypeScript/Rust/etc |
| Last Commit | YYYY-MM-DD |

## Activity (estimated)

| Period | Commits | Active Contributors |
|--------|---------|-------------------|
| Last 30 days | N | N |
| Last 90 days | N | N |
| Last year | N | N |

## Signals

- **Maintenance status:** [Active / Sporadic / Dormant / Archived]
- **Bus factor:** [1 / 2-3 / 4+ core contributors]
- **Issue responsiveness:** [Fast (<24h) / Moderate (1-7d) / Slow (>7d) / Unresponsive]
- **PR culture:** [Regular reviews / Self-merge / Sporadic]

## Raw Notes

[Any additional context, notable repos in the org, monorepo structure, etc.]

Read the full file on GitHub · 79 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. 2d ago First seen · 79 lines · 14 tokens per session scan A 544816d18c91

Subscribe to this mod's changes

data-github is an agent published in the GitHub repository golemfoundation/octant-council-builder (3 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 652 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-08-31.