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 jkomyno/.dotfiles --skill pr-descriptiongit clone --depth 1 https://github.com/jkomyno/.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/jkomyno/.dotfiles/pr-description)<a href="https://agentmods.dev/skills/jkomyno/.dotfiles/pr-description"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/pr-description/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/jkomyno/.dotfiles/pr-description"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/pr-description.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.00682 |
| Opus 5 | $0.00018 | $0.00341 |
| Sonnet 5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
pr-description 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 9d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR description
Describe the change a reviewer must evaluate. Keep the body aligned with the final committed diff, the repository template, and verification that actually ran.
Establish the boundary
- Inspect all Git remotes, the repository path, and local instructions before drafting.
- If the project belongs to Composio or is a fork or checkout of a Composio repository, stop using this skill. Use
composio-prwhen it covers that repository; otherwise follow its local guidance. - Draft only unless the user explicitly asked to create or update the live pull request.
Proceed only after confirming that the repository is outside Composio and whether the requested output is a draft or a live change.
Gather evidence
- Read repository instructions and every applicable pull request template, including templates under
.github/PULL_REQUEST_TEMPLATE/. - Establish the exact base and head. For an existing pull request, prefer its live GitHub refs and committed diff over stale local tracking branches.
- Read the commit list, diff stat, and full diff. Check the final working tree so uncommitted work is not described as shipped.
- Read the linked issue or user request when available.
- Record user-visible behavior, public contract changes, migration needs, risks, and verification results. Treat skipped or pending checks as missing evidence.
Finish this pass with every planned claim traceable to the diff, issue, or observed verification output.
Write the body
Honor required headings and checklists from the repository template. Within that structure, include only material that helps review:
- Lead with the concrete outcome and motivation when the motivation is not obvious.
- Describe behavioral and contract changes, using exact domain names and code identifiers.
- Explain migration steps for breaking changes with verified before-and-after usage when useful.
- Report only checks that completed, with commands or check names precise enough to identify them.
- Add issue links, screenshots, rollout notes, or risk notes only when they apply.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 61 lines · 37 tokens per session scan A 9372c225537d
pr-description is a skill published in the GitHub repository jkomyno/.dotfiles (5 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 682 once invoked, about $0.0002 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.