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.
git clone --depth 1 https://github.com/georgekhananaev/claude-skills-vaultWrote 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/commands/georgekhananaev/claude-skills-vault/create-pr)<a href="https://agentmods.dev/commands/georgekhananaev/claude-skills-vault/create-pr"><img src="https://agentmods.dev/badge/commands/georgekhananaev/claude-skills-vault/create-pr/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/commands/georgekhananaev/claude-skills-vault/create-pr"><img src="https://agentmods.dev/badge/commands/georgekhananaev/claude-skills-vault/create-pr.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.00010 | $0.00721 |
| Opus 5 | $0.00005 | $0.00360 |
| Sonnet 5 | $0.00002 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
pr 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pr — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Workflow
Execute this workflow to prepare a GitHub Pull Request:
1. Gather Branch Information
- Run
git branch --show-currentto get current branch name - Run
git config user.nameandgit config user.email - Show: "📍 Current branch: [branch_name]"
- Show: "👤 Author: [name] <[email]>"
2. Determine Base Branch
- Check if
mainormasterexists as the default branch - Use the appropriate base branch for comparison
3. Analyze Changes
- Run
git rev-list --count [base]..HEADto count commits - Run
git log [base]..HEAD --onelineto list all commits - Run
git diff [base]..HEAD --statto show changed files summary - Run
git diff [base]..HEADfor detailed changes (summarize, don't show all)
4. Generate PR Details
Present the PR information in this format:
## PR Title
<type>: <concise description>
## PR Description
### 📋 Summary
<2-3 sentence overview of what this PR does>
### 🔄 Changes
- Change 1: description
- Change 2: description
- Change 3: description
### 📁 Files Changed
- `path/to/file1.ts` - description of changes
- `path/to/file2.tsx` - description of changes
### 🧪 Testing
- [ ] Unit tests added/updated
- [ ] Manual testing completed
- [ ] No breaking changes
### 📝 Notes
<Any additional context, screenshots needed, or deployment notes>
5. ASK FOR APPROVAL
Stop here and ask:
Ready to create PR?
1. Copy details to clipboard (manual PR)
2. Create PR via GitHub CLI (gh pr create)
3. Edit details first
WAIT for my response before proceeding.
6. If Option 2 (GitHub CLI)
Run:
gh pr create --title "<title>" --body "<body>" --base [base_branch]
Show the PR URL when complete.
PR Title Types
feat: New featurefix: Bug fixdocs: Documentation changesstyle: Code style/formattingrefactor: Code refactoringtest: Adding/updating testschore: Maintenance tasksperf: Performance improvementsci: CI/CD changes
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.
- 12d ago First seen · 103 lines · 10 tokens per session scan A 75f30c6f1631
pr is a command published in the GitHub repository georgekhananaev/claude-skills-vault (28 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 721 once invoked, about $0.0001 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-30.
Other commands, from other repositories
quick-commit
Quick commit with automatic formatting, linting, and conventional commit message.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
resync
Resync external skill submodules to latest upstream versions.
commit
Analyze Git changes and generate a conventional commit message following the Commitizen format.
dependabot-merge
Interactively review and merge Dependabot PRs for a GitHub repo.
gh-release
Create a new GitHub release by triggering the Release workflow.