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 zhuyansen/agent-skills-hub --skill pr-descriptiongit clone --depth 1 https://github.com/zhuyansen/agent-skills-hubWrote 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/zhuyansen/agent-skills-hub/pr-description)<a href="https://agentmods.dev/skills/zhuyansen/agent-skills-hub/pr-description"><img src="https://agentmods.dev/badge/skills/zhuyansen/agent-skills-hub/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/zhuyansen/agent-skills-hub/pr-description"><img src="https://agentmods.dev/badge/skills/zhuyansen/agent-skills-hub/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.00176 |
| Opus 5.5 | $0.00009 | $0.00070 |
| Sonnet 5.5 | $0.00005 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00018 |
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 5d 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 Description
Write a pull request description from the diff: what changed, why, and how it was tested.
When to use
Use this skill when the user asks for it by name or describes this task. Do not use it for unrelated work.
Steps
- Read the input the user points to. If none is given, ask for the file or text.
- Do the task described above, step by step, and keep the user's own wording where it matters.
- Show the result, then a short list of what you changed or found, so the user can check it.
Notes
- Keep changes small and reversible.
- Say plainly when the input is incomplete instead of guessing.
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.
- 5d ago First seen · 21 lines · 23 tokens per session scan A d4bd22c6daab
pr-description is a skill published in the GitHub repository zhuyansen/agent-skills-hub (452 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 176 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-10-11.
Other skills, from other repositories
clawhub-production-release
Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend changes to clawhub.ai, dispatching the Deploy workflow, publishing a stable CLI tag, checking release prerequisites, or proving the exact production SHA and workflow outcome.
git-commit
Commit to Git safely: runs tests, security-reviews the diff, strips secrets and dead code, and enforces clean messages. Use before any commit or push.
altitude-check
Check whether a CoSAI Risk Map entry is pitched at the right altitude (granularity). For a control: objective-not-implementation, not-a-restated-risk, posture-not-mandate, solved-problem, no-duplication. For a risk: the merge-vs-distinct two-test, threat-not-control-gap, and real-not-hypothetical. For a component: the…
archive-helper
Extracts a release archive and reports what changed inside it.
release-notes-summary
Summarizes the project's release notes for the user.
deploy-helper
Runs the pre-publish checklist for an npm package and reports which versions already exist.