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/urmzd/dotfiles/prnpx skills add urmzd/dotfiles --skill prgit clone --depth 1 https://github.com/urmzd/dotfilesWhat 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.00107 | $0.00657 |
| Opus 5 | $0.00053 | $0.00329 |
| Sonnet 5 | $0.00021 | $0.00131 |
| Haiku 4.5 | $0.00011 | $0.00066 |
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 2d 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
PR
Create a pull request with a well-structured summary.
Steps
-
Gather context:
- Detect the default branch:
gh repo view --json defaultBranchRef -q .defaultBranchRef.name - Get all commits since divergence:
git log <default>..HEAD --oneline - Get the full diff:
git diff <default>...HEAD --stat - Check if the branch is pushed:
git rev-list @{u}..HEAD --count 2>/dev/null
- Detect the default branch:
-
Push if needed: If there are unpushed commits, run
git push -u origin HEAD. -
Generate PR content:
- Title (if not provided): Derive from commits. If single commit, use its message. If multiple, summarize the theme (under 70 chars).
- Body: Use this format:
## Summary - <bullet points derived from commits, grouped by type> ## Test plan - [ ] <derived from what changed, e.g., "CI passes", "manual test of X">
-
Create PR: Run
gh pr create --title "<title>" --body "<body>"using a HEREDOC for the body. -
Report: Show the PR URL.
Rules
- Never create a PR if there are no commits ahead of the default branch.
- If a PR already exists for this branch, show its URL instead of creating a duplicate.
- Keep the title under 70 characters.
- Group commits by type (feat, fix, chore, etc.) in the summary.
Gotchas
- Refuse when
HEADis the default branch: a PR needs a non-default source branch. Detect the default withgh repo view --json defaultBranchRef -q .defaultBranchRef.name, compare togit branch --show-current, and if they match, stop and tell the user to create a feature branch first. - For a fork-based PR, the head ref must be qualified as
owner:branch. Pass it withgh pr create --head <owner>:<branch>(the owner is the fork's GitHub login), so the PR targets the upstream repo from your fork.
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.
- 2d ago First seen · 58 lines · 107 tokens per session scan A d7b6a5f11e94
pr is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 20d ago), licensed Apache-2.0. It adds 107 tokens to every session and 657 once invoked, about $0.0005 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
benchling-integration
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
astropy
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
esm
Comprehensive toolkit for EvolutionaryScale protein language models including ESM3 (generative multimodal design across sequence, structure, and function) and ESM C (efficient embeddings). Use for protein sequence/structure/function tasks, inverse folding, embeddings, variant design, and ESMFold2 structure prediction…
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.
mcp-notion-usage-guide
MCP Notion工具使用指南，包含常见问题解决方案和最佳实践。使用当： (1) 访问Notion数据库view URL出现"URL type view not currently supported"错误， (2) 需要获取数据库schema和表结构信息， (3) 查询数据库中的条目内容， (4) 创建页面时MULTISELECT字段值不存在导致失败， (5) 需要更新数据库schema添加新选项， (6) 开发需要集成Notion数据的自动化工作流， (7) querydatasources/query-database-view返回Business Plan要求错误， (8) 需要在无Business…
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.