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.
git clone --depth 1 https://github.com/Amey-Thakur/AI-SKILLSWrote 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/commands/amey-thakur/ai-skills/pr-description)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/pr-description"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/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/commands/amey-thakur/ai-skills/pr-description"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/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.00023 | $0.00318 |
| Opus 5 | $0.00012 | $0.00159 |
| Sonnet 5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
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 4d 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
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Write a pull request description for this change:
{diff}
Context: {context}
Structure:
- Title: a concise summary of the change (imperative, specific).
- What and why: what this PR does and the problem it solves, in a few sentences. Lead with the reason a reviewer should care.
- Changes: the key changes as a short list, so a reviewer knows where to look and in what order to read.
- How to test / verify: the concrete steps or the automated coverage that proves it works, plus anything that needs manual checking.
- Risk and rollout: anything risky (migrations, breaking changes, config), and how to roll back if needed. Note out-of-scope items deliberately left out.
- Link the issue/ticket.
Rules: write for the reviewer's time: help them review well and fast. Keep the PR's actual scope honest (if the diff does two unrelated things, suggest splitting). No filler; every line helps someone review or merge. Output the description in markdown, ready to paste.
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.
- 4d ago First seen · 38 lines · 23 tokens per session scan A 98d6b36a2310
pr-description is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 318 once invoked, about $0.0001 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-09-06.
Other commands, from other repositories
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
pr-reviewer
Review a Git branch as a PR against the base branch (auto-resolved — main/master) judged by THIS repo's contract (CLAUDE.md + .claude/skills/). Three-dot diff, route changed paths to skills, verify (eslint/prettier/tsc + tests), tiered report + confidence. Optional gated fix + commit after the report.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
commit-and-create-mr
Commit and create MR on Gitlab.
review
Recent git commits: !git log --oneline -10.
pr-package
Prepare a clean delivery package for GitHub from the real git diff vs an explicit base branch, persisted as PRPACKAGE.md (or PRPACKAGE. .md for multi-repo tasks). Produces branch name, commit messages, fetch, checkout, add, commit, and push commands, PR title and body, and reviewer attention points; never invents work…