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 fredrikaverpil/dotfiles --skill gh-prgit clone --depth 1 https://github.com/fredrikaverpil/dotfilesWrote 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/fredrikaverpil/dotfiles/gh-pr)<a href="https://agentmods.dev/skills/fredrikaverpil/dotfiles/gh-pr"><img src="https://agentmods.dev/badge/skills/fredrikaverpil/dotfiles/gh-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/skills/fredrikaverpil/dotfiles/gh-pr"><img src="https://agentmods.dev/badge/skills/fredrikaverpil/dotfiles/gh-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 1 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00039 | $0.00178 |
| Opus 5.5 | $0.00016 | $0.00071 |
| Sonnet 5.5 | $0.00008 | $0.00036 |
| Haiku 4.5 | $0.00004 | $0.00018 |
Grade A, and why
gh-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 7d 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
GitHub Pull Request Creation with gh
When creating a pull request with the gh CLI, use the command template below.
For the title and body content, follow the "pr-style" skill (conventional
commit title, Why/What/Notes body, draft PRs).
Command Template
gh pr create --draft --assignee @me --title "<title>" --body "$(cat <<'EOF'
body here
EOF
)"
Rules
- Always create draft PRs (
--draft) - Always assign the PR to me (
--assignee @me)
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.
- 7d ago Changed · +28 lines · +39 tokens per session b271d40630bc
- 1mo ago First seen · 1 lines · 0 tokens per session scan A bba61862f2b6
gh-pr is a skill published in the GitHub repository fredrikaverpil/dotfiles (259 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 178 once invoked, about $0.0002 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
pr
Use when the user wants to create a new pull request, update an existing PR's body, open a draft PR, or preview a PR body locally before pushing.
pr-grooming
Use when the user wants to groom, triage, or clean up the open pull requests of a repo: "groom the PRs", "review the open PRs", "which drafts are stale", "close old draft PRs", "rebase the dependabot PRs", "are the open PRs still mergeable", "refresh that old bugfix PR", or a periodic PR review — even when they do not…
review-pr
Review and merge GitHub pull requests for Spatie packages. Use when asked to review a PR, review a pull request, merge a PR, or when given a GitHub PR URL to review. Also triggers on 'review this PR,' 'check this pull request,' 'merge this,' or '/review-pr'. Uses gh CLI for all GitHub operations.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.