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 curie-eng/curie --skill github-activitygit clone --depth 1 https://github.com/curie-eng/curieWrote 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/curie-eng/curie/github-activity)<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.
<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>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.00054 | $0.00552 |
| Opus 5.5 | $0.00022 | $0.00221 |
| Sonnet 5.5 | $0.00011 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
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.
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
- Work out the window.
sinceis the start as ISO 8601 (for example2026-09-28T00:00:00Z): the last run time when this is a recurring report, otherwise the date the user named.untilis optional and defaults to now. - Call
repository_activityon thegithubserver withsince, anduntilwhen the user gave an end. Passrepositories(a list ofowner/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. - 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.
- 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 latersinceor an earlieruntil). 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.
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 First seen · 42 lines · 54 tokens per session scan A 76d99ef784b0
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.
Other skills, from other repositories
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
radin-batch
Work backlog tasks via sub-agents, prioritized, one commit each; asks whether to plan each task first. Use for "work through my backlog", "skip planning", or name an epic or task to run only those.
implement-issue
Implements an issue end-to-end: fetches the spec from the project issue tracker, creates branch, writes code with TDD, runs checks, commits, publishes a draft change (PR/MR), closes issue on merge. Tracker- and host-agnostic — GitHub via gh CLI is the factory default; docs/agents/issue-tracker.md and…
git-commit
A Git workflow for creating Conventional Commits messages from actual workspace changes and, when requested, committing or pushing them.