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 agentmods add skills/theagenticguy/opencodehub/codehub-pr-descriptionnpx skills add theagenticguy/opencodehub --skill codehub-pr-descriptiongit clone --depth 1 https://github.com/theagenticguy/opencodehubWhat 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 | $0.00126 | $0.01345 |
| Opus 5 | $0.00063 | $0.00673 |
| Sonnet 5 | $0.00025 | $0.00269 |
| Haiku 4.5 | $0.00013 | $0.00135 |
Grade A, and why
codehub-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 yesterday.
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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codehub-pr-description
Generates a Markdown PR body from graph primitives. Linear (no subagents). Sonnet. Refuses on a clean tree.
Preconditions
- Resolve
--base(defaultmain) and--head(defaultHEAD) viagit rev-parse. git diff --name-only <base>..<head>must return ≥ 1 path. If empty, emitNo diff detected — resolve base/head or stage changes.and stop. (Spec 001 AC-5-4.)
Arguments
--base <rev>— base revision. Default:main.--head <rev>— head revision. Default:HEAD.--out <path>— output path. Default:.codehub/pr/PR-<branch>.md.
Process
- Run the preconditions. On clean tree, refuse and stop.
mcp__codehub__detect_changes({base, head})— map the diff to affected symbols + processes.mcp__codehub__verdict({base, head})— 5-tier merge recommendation with reasons.mcp__codehub__owners({paths: <changed-files>})— required reviewers per path.mcp__codehub__list_findings_delta({base, head})— new/resolved scanner findings in the diff range.- For any symbol flagged as tier ≥ 3 by verdict:
mcp__codehub__impact({symbol, direction: "downstream", depth: 2})— spell out who breaks. - For public API changes:
mcp__codehub__api_impact({route})when the diff touches a handler. - Assemble the Markdown body using the template below.
Writeto<out>.
Output template
# <branch-name or commit subject>
## Summary
2–3 sentences describing what this PR changes and why. Grounded in the
commit messages + the highest-impact change detected.
## Verdict
**Tier <N> — <label>** per `mcp__codehub__verdict`.
Reasons:
- ... (from verdict.reasons[])
## Affected surface
| Category | Count | Details |
|---|---|---|
| Files changed | N | `git diff --stat` summary |
| Symbols added | N | from `detect_changes` |
| Symbols removed | N | from `detect_changes` |
| Processes touched | N | from `detect_changes.processes[]` |
### Top touched files
| File | Change | Top owner |
|---|---|---|
| `packages/foo/src/bar.ts` | +40 / -12 | alice@ |
| ... | ... | ... |
## Blast radius
(Only when verdict tier ≥ 3.)
- Downstream consumers of `<symbol>`: <count>. See `impact` output.
- Affected routes: (if `api_impact` returned non-empty)
## Findings delta
| Change | Severity | File |
|---|---|---|
| new | error | `packages/foo/src/bar.ts:42` |
| resolved | warn | `packages/other.ts:88` |
(Or: "No new findings. 2 findings resolved." as a terse summary.)
## Required reviewers
- `packages/foo/` — alice@, bob@
- `packages/other/` — charlie@
## Test plan
- [ ] ...
- [ ] ...
(Extract TODO-shaped lines from `git log <base>..<head>` or leave a blank checklist for the author to fill in.)
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.
- yesterday First seen · 123 lines · 126 tokens per session scan A e441a63add08
codehub-pr-description is a skill published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 20d ago), licensed Apache-2.0. It adds 126 tokens to every session and 1,345 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…