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/juxt/claude-plugins/prnpx skills add juxt/claude-plugins --skill prgit clone --depth 1 https://github.com/juxt/claude-pluginsWhat 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.00130 | $0.01541 |
| Opus 5 | $0.00065 | $0.00771 |
| Sonnet 5 | $0.00026 | $0.00308 |
| Haiku 4.5 | $0.00013 | $0.00154 |
Grade A, and why
pr 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 2d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request
Interpret MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, etc. per RFC 2119.
The user MAY provide a PR title as an argument (e.g. /chalk:pr feat: read-only secondaries).
If no title is provided, draft one from the branch's commits.
Before you draft
A PR description is an explanation artefact, and it MUST be drafted against the chalk voice. Load these first (via the Skill tool):
chalk:voice, and itsreferences/palette.md— the principles, the section palette, the line-format rule.chalk:mindmap— the shape of the content inside each section.chalk:goal-tree, where a section states what the work has to achieve rather than what it did — a Future state section, or the remaining steps of a change landing in pieces. A PR's Implementation section is retrospective ("what landed") and doesn't want one.
Structure the description into sections drawn from the palette, choosing the ones this change needs, and write each section as a mindmap — a short tl;dr opening it, then the tree. A wall of undifferentiated prose is the wrong shape; if you've written one, you skipped this step.
Your audience is a reviewer about to read the diff, who didn't see the branch and hasn't yet opened the linked issue, but can.
A PR is the moment the rest of the team learns the change exists, and that reviewer is deciding two things: whether this affects them, and whether the approach holds.
Write the summary for them — see "Name your audience" in chalk:voice, and the tl;dr rules in chalk:mindmap.
Your responsibilities
-
Gather context.
- Review the commits on this branch — all of them, not just the latest.
- Review the conversation history for context that isn't in the commits.
- If chalk is active, read all chalk comments on the tracked issue via the github agent.
- Identify the base branch.
-
Draft a title — the user's if given, otherwise a short one that captures the intent.
-
Draft the description.
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.
- 2d ago First seen · 90 lines · 130 tokens per session scan A e9bee19542c6
pr is a skill published in the GitHub repository juxt/claude-plugins (10 stars, last pushed 4d ago), licensed MIT. It adds 130 tokens to every session and 1,541 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…