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 agentmods add skills/wrannaman/agentic-engineering/gh-summarynpx skills add wrannaman/agentic-engineering --skill gh-summarygit clone --depth 1 https://github.com/wrannaman/agentic-engineeringWrote 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/wrannaman/agentic-engineering/gh-summary)<a href="https://agentmods.dev/skills/wrannaman/agentic-engineering/gh-summary"><img src="https://agentmods.dev/badge/skills/wrannaman/agentic-engineering/gh-summary.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.01227 |
| Opus 5 | $0.00019 | $0.00613 |
| Sonnet 5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
gh-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 4d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Contribution Summary
Summarize merged PRs and interpret the business/engineering value delivered.
Usage
/gh-summary- Current repo, last 30 days/gh-summary last 7 days- Current repo, last 7 days/gh-summary since January 1st- Current repo, since date/gh-summary owner/repo1 owner/repo2 last 30 days- Multiple repos
Arguments
Arguments can be provided in any order. The skill will parse:
-
Repos (optional): Comma or space-separated list of repos in
owner/repoformat- If omitted, uses the current working directory's repo
- Examples:
owner/repo-name,owner/repo1,owner/repo2
-
Time range (optional): Natural language time specification
- Relative: "last 7 days", "last 2 weeks", "last 30 days"
- Absolute: "since January 1st", "since 2026-01-01"
- If omitted, defaults to "last 30 days"
Process
Step 1: Parse Arguments
Parse the ARGUMENTS string to extract:
- repos: List of repos, or empty (meaning current repo)
- time_range: Natural language time, or "last 30 days" default
Convert time range to ISO date format (YYYY-MM-DD) for the gh search query.
Step 2: Get GitHub Username
gh api user --jq '.login'
Step 3: Fetch PRs for Each Repo
For each repo (or current repo if none specified):
gh pr list --repo {repo} --author {username} --state merged \
--search "merged:>={iso_date}" --limit 200 \
--json number,title,body,mergedAt,additions,deletions,changedFiles,commits,url
If no --repo flag needed (current repo), omit it:
gh pr list --author {username} --state merged \
--search "merged:>={iso_date}" --limit 200 \
--json number,title,body,mergedAt,additions,deletions,changedFiles,commits,url
Step 4: Calculate Stats
From the PR data, calculate:
- PR count: Total number of PRs merged
- Lines added: Sum of
additionsacross all PRs - Lines removed: Sum of
deletionsacross all PRs - Net lines: additions - deletions
- Files changed: Sum of
changedFilesacross all PRs - Commits: Sum of commit counts (length of
commitsarray) across all PRs - Repos touched: Count of unique repos (if multi-repo)
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.
- 4d ago First seen · 141 lines · 39 tokens per session scan A 9b220cda4c34
gh-summary is a skill published in the GitHub repository wrannaman/agentic-engineering (2 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 1,227 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…