Borrowing it
Nothing to install: this file belongs to harukiseller-droid/commerce-agent-bench. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/harukiseller-droid/commerce-agent-bench/main/.agents/skills/pr-draft-summary/SKILL.mdgit clone --depth 1 https://github.com/harukiseller-droid/commerce-agent-benchWrote 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/harukiseller-droid/commerce-agent-bench/pr-draft-summary)<a href="https://agentmods.dev/skills/harukiseller-droid/commerce-agent-bench/pr-draft-summary"><img src="https://agentmods.dev/badge/skills/harukiseller-droid/commerce-agent-bench/pr-draft-summary/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/harukiseller-droid/commerce-agent-bench/pr-draft-summary"><img src="https://agentmods.dev/badge/skills/harukiseller-droid/commerce-agent-bench/pr-draft-summary.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.00017 | $0.00283 |
| Opus 5.5 | $0.00007 | $0.00113 |
| Sonnet 5.5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
pr-draft-summary 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.
What it actually says
PR Draft Summary
Purpose
Turn verified implementation evidence into a concise reviewer-facing pull-request description.
When to use
Use before opening or updating a pull request after implementation and verification.
Inputs
- final diff and changed files;
- issue or task scope;
- commands actually run and their outputs;
- known limitations and reviewer risks.
Required checks
Confirm the summary covers:
- What changed
- Why
- Tests run
- Eval results
- Known limitations
- Risk
- Reviewer focus
Separate repository facts from assumptions and link exact evidence where possible.
Output contract
Return these headings in this order:
## What changed
## Why
## Tests run
## Eval results
## Known limitations
## Risk
## Reviewer focus
Use plain factual language. Include Codex benchmark execution: NOT RUN unless a real Codex execution artifact exists.
Failure conditions
- Do not use marketing language or inflate adoption, usage, stars, contributors, or performance.
- Do not report guessed test results.
- Do not create
codex-output.md,patch.diff, orresult.jsonwithout an actual execution.
Verification
Compare every statement with the final diff, command output, and repository state before publishing the summary.
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 · 61 lines · 17 tokens per session scan A c690a673e463
pr-draft-summary is a skill published in the GitHub repository harukiseller-droid/commerce-agent-bench (101 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 283 once invoked, about $0.0001 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
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.
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.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.