github-activity

github-activity is a skill for Claude Code from curie-eng/curie. It costs 54 tokens per session (552 once invoked), scanned A, original, Apache-2.0.

A read-only workflow that reports activity across GitHub repositories during a chosen time window. It summarizes merged pull requests, opened and closed issues, and changes to milestones.

In plain words
What is it for?
It is for producing reports such as what merged since Monday, which issues changed, and what moved since the last release.
Why use it?
It removes the need to inspect several repositories manually for a recurring progress update.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the github-activity plugin — 1 skill shipped together

Good fit It is for producing reports such as what merged since Monday, which issues changed, and what moved since the last release.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/curie-eng/curie/github-activity
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.

Any agent
npx skills add curie-eng/curie --skill github-activity
Clone the repo
git clone --depth 1 https://github.com/curie-eng/curie

Made for: Claude Code.

Or install github-activity, the plugin that ships this one along with the rest of its 1 skill.

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 github-activity

README.md
[![agentmods](https://agentmods.dev/badge/skills/curie-eng/curie/github-activity/github.svg)](https://agentmods.dev/skills/curie-eng/curie/github-activity)
Your own site
<a href="https://agentmods.dev/skills/curie-eng/curie/github-activity"><img src="https://agentmods.dev/badge/skills/curie-eng/curie/github-activity/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.

agentmods 80×15 button for github-activity

Your own site · 80×15
<a href="https://agentmods.dev/skills/curie-eng/curie/github-activity"><img src="https://agentmods.dev/badge/skills/curie-eng/curie/github-activity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 552 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00054 $0.00552
Opus 5.5 $0.00022 $0.00221
Sonnet 5.5 $0.00011 $0.00110
Haiku 4.5 $0.00005 $0.00055

Measured yesterday against content hash 76d99ef784b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

github-activity 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.

examples/github-activity/skills/github-activity/SKILL.md · 42 lines

How it starts

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

GitHub activity over a window

When to run

The user wants a summary of repository activity since a point in time: merged pull requests, issues opened and closed, and milestone movement, usually across several repositories at once. Typical asks are "what merged since Monday" or "what changed since my last update".

How to answer

  1. Work out the window. since is the start as ISO 8601 (for example 2026-09-28T00:00:00Z): the last run time when this is a recurring report, otherwise the date the user named. until is optional and defaults to now.
  2. Call repository_activity on the github server with since, and until when the user gave an end. Pass repositories (a list of owner/name) only when the user named specific ones; otherwise the configured set is used. If the tool says no repositories are configured, ask which to read.
  3. Report per repository, in this order, leaving out empty sections:
    • merged pull requests: number, title, author, merge time;
    • issues opened: number, title, author;
    • issues closed in the window, even if reopened since: number, title, and whether completed or not planned when GitHub reports it;
    • milestone movement: items added to or removed from a milestone, and milestones created or closed in the window. If every list is empty for a repository and nothing was truncated, say it was quiet in one line.
  4. Read truncated. When it is non-empty for a repository, say plainly that the window was too busy to read in full for that repository, name what was cut off, and suggest a narrower window (a later since or an earlier until). Never describe a truncated repository as quiet or complete.

What this bundle cannot do

It cannot write to GitHub. There is no tool for commenting, labeling, closing, reopening, assigning, or moving an issue or pull request to a milestone, and the credential behind it is read only. When asked for any of those, say this bundle is read only and cannot make the change; offer the details the person would need to make it themselves.

Read the full file on GitHub · 42 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. yesterday First seen · 42 lines · 54 tokens per session scan A 76d99ef784b0

Subscribe to this mod's changes

github-activity is a skill published in the GitHub repository curie-eng/curie (37 stars, last pushed today), licensed Apache-2.0. It adds 54 tokens to every session and 552 once invoked, about $0.0002 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-10-15.