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 shousper/claude-kit --skill github-work-summarygit clone --depth 1 https://github.com/shousper/claude-kitWrote 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/shousper/claude-kit/github-work-summary)<a href="https://agentmods.dev/skills/shousper/claude-kit/github-work-summary"><img src="https://agentmods.dev/badge/skills/shousper/claude-kit/github-work-summary/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/shousper/claude-kit/github-work-summary"><img src="https://agentmods.dev/badge/skills/shousper/claude-kit/github-work-summary.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.00110 | $0.01248 |
| Opus 5.5 | $0.00044 | $0.00499 |
| Sonnet 5.5 | $0.00022 | $0.00250 |
| Haiku 4.5 | $0.00011 | $0.00125 |
Grade A, and why
github-work-summary 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Work Summary
Overview
Generates a comprehensive work summary from a user's GitHub activity (PRs, issues) for a specified time period and organization, using the gh CLI for data collection and parallel subagents for detail fetching.
When to Use
- User asks "what did I do last week?" or similar
- User needs a weekly/monthly work summary or standup notes
- User wants to review contributions across an organization
- User needs to compile accomplishments for a performance review or report
Not for: Repository-level changelogs, release notes, or team-wide activity reports.
Process
Copy this checklist and track progress:
Work Summary Progress:
- [ ] Step 1: Clarify parameters (period, org)
- [ ] Step 2: Run data collection script
- [ ] Step 3: Launch parallel subagents for detail fetching
- [ ] Step 4: Analyze contributions
- [ ] Step 5: Generate categorized summary
Step 1: Clarify Parameters
Determine two inputs from your human partner's request:
| Parameter | Default | Examples |
|---|---|---|
| Period | "last week" | "this week", "last month", "last 14 days", "2026-01-01 to 2026-01-31" |
| Organization | Ask user | "ethpandaops", "*" for all orgs |
If either is ambiguous, ask before proceeding.
Step 2: Run Data Collection Script
Run the categorization script:
python3 skills/github-work-summary/scripts/collect_activity.py "<period>" "<org>" "<today_date>"
The script outputs JSON with all matching PRs and issues. Capture this output for Step 3.
If the script fails: Verify gh CLI is installed and authenticated (gh auth status). The user must be logged in.
Step 3: Fetch Details with Parallel Subagents
CRITICAL: Launch ALL detail-fetching agents in a SINGLE message using multiple parallel subagent-delegation calls for maximum speed.
For each PR in the JSON output, create one subagent:
gh pr view <number> --repo <owner/repo> --json body,comments,author,commits
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 142 lines · 110 tokens per session scan A 71665653d0db
github-work-summary is a skill published in the GitHub repository shousper/claude-kit (4 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 1,248 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.