rtk is a command-line proxy that filters and compresses output from development commands before it reaches an LLM's context. It is used with coding agents to reduce the tokens consumed by commands such as Git operations. The catalogue includes skills, commands, agents, and instructions for using rtk in agent workflows.
Borrowing it
Nothing to install: this file belongs to rtk-ai/rtk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rtk-ai/rtk/develop/.claude/skills/repo-recap/SKILL.mdgit clone --depth 1 https://github.com/rtk-ai/rtkWrote 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/rtk-ai/rtk/repo-recap)<a href="https://agentmods.dev/skills/rtk-ai/rtk/repo-recap"><img src="https://agentmods.dev/badge/skills/rtk-ai/rtk/repo-recap/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/rtk-ai/rtk/repo-recap"><img src="https://agentmods.dev/badge/skills/rtk-ai/rtk/repo-recap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector pass
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.00034 | $0.01814 |
| Opus 5.5 | $0.00014 | $0.00726 |
| Sonnet 5.5 | $0.00007 | $0.00363 |
| Haiku 4.5 | $0.00003 | $0.00181 |
Grade A, and why
repo-recap 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Recap
Generate a structured recap of the repository state: open PRs, open issues, recent releases, and executive summary. Output is formatted as Markdown with clickable GitHub links, ready to share.
Language
- Check the argument passed to this skill
- If
enorenglish→ produce the recap in English - If
fr,french, or no argument → produce the recap in French (default)
Preconditions
Before gathering data, verify:
# Must be inside a git repo
git rev-parse --is-inside-work-tree
# Must have gh CLI authenticated
gh auth status
If either fails, stop and tell the user what's missing.
Steps
1. Gather Data
Run these commands in parallel via gh CLI:
# Repo identity (for links)
gh repo view --json nameWithOwner -q .nameWithOwner
# Open PRs with metadata
gh pr list --state open --limit 50 --json number,title,author,createdAt,changedFiles,additions,deletions,reviewDecision,isDraft
# Open issues with metadata
gh issue list --state open --limit 50 --json number,title,author,createdAt,labels,assignees
# Recent releases (for version history)
gh release list --limit 5
# Recently merged PRs (for contributor activity)
gh pr list --state merged --limit 10 --json number,title,author,mergedAt
Note: author in JSON results is an object {login: "..."} — always extract .author.login when processing.
2. Determine Maintainers
To distinguish "our PRs" from external contributions:
gh api repos/{owner}/{repo}/collaborators --jq '.[].login'
If this fails (permissions), fallback: authors with write/admin access are those who merged PRs recently. When in doubt, ask the user.
3. Analyze and Categorize
PRs — Categorize into 3 groups:
Our PRs (author is a repo collaborator):
- List with PR number (linked), title, size (+additions, files count), status
External — Reviewable (manageable size, no major blockers):
- Additions ≤ 1000 AND files ≤ 10
- No merge conflicts, CI not failing
- Include: PR link, author, title, size, review status, recommended action
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 · 217 lines · 34 tokens per session scan A 165e7ac9fda7
repo-recap is a skill published in the GitHub repository rtk-ai/rtk (84,655 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 1,814 once invoked, about $0.0001 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-30.
Other skills, from other repositories
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.
talk-stage2-research
Performs git archaeology, changelog analysis, and builds a verified factual timeline by cross-referencing git history with source material. REX mode only (skipped automatically in Concept mode). Use when building a REX talk and you need verified commit metrics, release timelines, and contributor data from a git…
verify-release
Use when checking whether a Proofpack release candidate has complete local evidence before packaging.