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 martinemde/dotfiles --skill prgit clone --depth 1 https://github.com/martinemde/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/martinemde/dotfiles/pr)<a href="https://agentmods.dev/skills/martinemde/dotfiles/pr"><img src="https://agentmods.dev/badge/skills/martinemde/dotfiles/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/martinemde/dotfiles/pr"><img src="https://agentmods.dev/badge/skills/martinemde/dotfiles/pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00047 | $0.00661 |
| Opus 5.5 | $0.00019 | $0.00264 |
| Sonnet 5.5 | $0.00009 | $0.00132 |
| Haiku 4.5 | $0.00005 | $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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
/pr— draft PR for the current diff from trunk/pr [revision]— draft PR for that revision/pr [revision] ready— ready for review rather than draft
Push and get the bookmark
The command depends on what the revision already has:
jj git push --bookmark <name> # remote-tracked bookmark
jj bookmark track <name>@origin && jj git push --bookmark <name> # local-only bookmark
jj git push -c <revision> # no bookmark: creates one
Take the bookmark name from the output.
Review the whole changeset
jj log -r 'trunk()..<bookmark>' # commits going in
jj diff --from trunk() --to <bookmark> --stat # everything changing
A PR is easier to review as several focused commits than one large one. If the changeset is mixed,
reorganize with jj split or jj squash before opening it.
Check .github/ for a PR template and follow it if one exists.
Draft the title and body
The title summarizes the whole changeset, not just the most recent commit.
The body explains why the change was made and what it affects — context and motivation, not implementation. Don't restate what the diff already shows: "added function X" and "modified file Y" earn their place only when the reasoning behind them isn't obvious. Cover user-facing impact, architectural decisions, and trade-offs, following whatever conventions the repository already uses.
Two skills help here when they're available in the session. Invoke
elements-of-style:writing-clearly-and-concisely before drafting prose. Search
episodic-memory:search for conversations touching the changed files, looking for design
decisions and their rationale, alternatives that were considered and rejected, trade-offs, and
constraints that shaped the solution — surface what you find as a "Design Decisions" section.
Attribution gets an "Assisted-by" footer, not a "Generated with Claude Code" one.
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 · 72 lines · 47 tokens per session scan A 519316c879f5
pr is a skill published in the GitHub repository martinemde/dotfiles (10 stars, last pushed yesterday), licensed ISC. It adds 47 tokens to every session and 661 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-31.
Other skills, from other repositories
github-pull-request
Open, update, and verify GitHub pull requests.
merge-ready
Drive an existing pull request to a mergeable state: get CI green, resolve merge conflicts with the base branch, address and resolve review comments, trigger required bot reviews/approvals (e.g. commenting '@claude review'), link associated issues, and clean up the PR title and description. Ends with a readiness…
pr-create
Open a GitHub PR with a tight body — why this change, what'll surprise the reviewer, how we know it's correct — or add a pullrequesttemplate to a repo. Use when asked to open, create, or draft a pull request, compose or regenerate a PR description, or scaffold a repo's PR template. Composes the…
gh-pr
This skill should be used when creating a GitHub pull request via gh pr create. Covers the gh CLI mechanics; PR title and body conventions come from the pr-style skill.
lightjj
Interacts with a running lightjj instance (browser-based Jujutsu/jj viewer) via the lightjj api CLI. Reads diffs, posts inline review comments, posts doc-mode suggestions, and steers the user's view. Use when the user has lightjj running and wants the agent to review changes, annotate diffs, or comment on markdown…
github-pr-workflow
Working with GitHub Pull Requests using the gh CLI. Use for fetching PR details, review comments, CI status, and understanding the difference between PR-level comments vs inline code review comments.