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 viknesh20-20/claude-code-tool-kit --skill pr-summarygit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-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/viknesh20-20/claude-code-tool-kit/pr-summary)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/pr-summary"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/pr-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/viknesh20-20/claude-code-tool-kit/pr-summary"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/pr-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.00037 | $0.00472 |
| Opus 5.5 | $0.00015 | $0.00189 |
| Sonnet 5.5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
pr-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.
What it actually says
Generate PR Summary
Branch Context
!git branch --show-current 2>/dev/null
!git log main..HEAD --oneline 2>/dev/null || git log master..HEAD --oneline 2>/dev/null
Diff Summary
!git diff main...HEAD --stat 2>/dev/null || git diff master...HEAD --stat 2>/dev/null
Full Diff
!git diff main...HEAD 2>/dev/null | head -800 || git diff master...HEAD 2>/dev/null | head -800
Instructions
Step 1: Analyze All Commits
Read every commit message and the full diff. Understand:
- What feature, fix, or change was implemented
- Why it was needed (from commit messages and code context)
- What files were touched and what changed in each
Step 2: Generate PR Description
Use this format:
## Summary
<!-- 1-3 sentences explaining what this PR does and why -->
## Changes
<!-- Bulleted list of specific changes, grouped by area -->
### [Area 1]
- Change description
### [Area 2]
- Change description
## Test Plan
- [ ] Test case 1
- [ ] Test case 2
- [ ] Edge case verification
## Breaking Changes
<!-- List any breaking changes, or "None" -->
## Notes for Reviewers
<!-- Anything reviewers should pay special attention to -->
Step 3: Determine PR Title
- Format:
type: concise description(under 72 chars) - Types: feat, fix, refactor, docs, test, chore, perf
- Example:
feat: add user authentication with JWT refresh tokens
Rules
- Read ALL commits, not just the latest
- Don't embellish — describe what actually changed
- Flag any TODOs or known issues honestly
- Include breaking changes prominently
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 · 69 lines · 37 tokens per session scan A fdecbcedb6d7
pr-summary is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 472 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-31.
Other skills, from other repositories
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
aidlc-portfolio
Coordinate multiple AI-DLC workflows across repositories and Git worktrees using an evidence-backed portfolio catalog and deterministic workspace tooling. Use when initializing an AI-DLC portfolio workspace, discovering organization or business context, registering projects and dependencies, creating child intents and…
github
Use gh as the primary interface for GitHub data and actions. Keep this skill focused on basic operations and command safety, not maintainer triage strategy.