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 divinevideo/divine-mobile --skill pr-summarygit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/divinevideo/divine-mobile/pr-summary)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/pr-summary"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/pr-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/divinevideo/divine-mobile/pr-summary"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/pr-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.00045 | $0.00786 |
| Opus 5.5 | $0.00018 | $0.00314 |
| Sonnet 5.5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
pr-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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Summary Skill
Purpose
Generate a pull request description that follows the project's
.github/pull_request_template.md format. Analyzes all changes on the
current branch compared to main and produces a concise, ready-to-paste
PR body.
Workflow
Step 1: Gather Context
# Current branch name
git branch --show-current
# Commits on this branch vs main
git log main..HEAD --oneline
# Files changed with stats
git diff main...HEAD --stat
# Full diff for analysis
git diff main...HEAD
Step 2: Detect Issue Number
Look for the related issue number from (in priority order):
- Argument passed to the skill
- Branch name (e.g.,
fix/explore-hashtags-empty-view-> search issues) - Commit messages (e.g.,
Closes #1461)
Step 3: Analyze Changes
Read the diff and identify:
- What the change does (1-3 sentences max)
- Which type of change it is (bug fix, feature, refactor, etc.)
- Key architectural decisions (layers affected, new files, patterns used)
Step 4: Output
Output the PR body as a raw markdown code block so the user can copy-paste it directly into the GitHub PR description field.
Wrap the entire output in a fenced code block with the markdown language tag:
```markdown
<the PR body here>
```
Output Template
The content inside the code block must follow this structure exactly:
## Description
[1-3 sentence summary of what changed and why]
**Related Issue:** Closes #[number]
## Type of Change
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
- [ ] Code refactor
- [ ] Build configuration change
- [ ] Documentation
- [ ] Chore
Only check the applicable type ([x]). Keep the description short and focused
on the "what" and "why", not implementation details. Reviewers can read
the diff for the "how".
Rules
- Output as code block: Always wrap the full PR body in a
```markdownfenced code block so the user can copy-paste directly into GitHub. - Be concise: 1-3 sentences for description. No implementation details.
- Follow the template exactly: Use the checkboxes from
pull_request_template.md. - Single type: Only check one type of change unless it genuinely spans multiple.
- Link the issue: Always include
Closes #Nif an issue is known. - No emoji in description: The template already has emoji in the type checkboxes.
- No file lists or tables: The diff is available for reviewers. Don't duplicate it.
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 · 110 lines · 45 tokens per session scan A 59f355800d37
pr-summary is a skill published in the GitHub repository divinevideo/divine-mobile (264 stars, last pushed today), licensed MPL-2.0. It adds 45 tokens to every session and 786 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-09-03.
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.