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 juxt/claude-plugins --skill issuegit clone --depth 1 https://github.com/juxt/claude-pluginsWrote 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/juxt/claude-plugins/issue)<a href="https://agentmods.dev/skills/juxt/claude-plugins/issue"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/issue/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/juxt/claude-plugins/issue"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/issue.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.00141 | $0.03340 |
| Opus 5.5 | $0.00056 | $0.01336 |
| Sonnet 5.5 | $0.00028 | $0.00668 |
| Haiku 4.5 | $0.00014 | $0.00334 |
Grade A, and why
issue 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.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue
Interpret MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, etc. per RFC 2119.
This skill owns the issue description — drafting it, filing the issue, and correcting the description afterwards.
Which sections the body gets comes from chalk:voice's references/palette.md; this skill covers what an issue is for, and how it gets filed.
An issue is a living document. It states the problem as it is now, written as if it had always been that way. A PR freezes at merge; an issue has a mechanism for resolving what it doesn't yet know, which is why it MAY hold marked speculation and MUST be corrected as facts change.
Your readers
chalk:voice says who they are; here they are doing one of three things, and none of them is deciding whether the work is worth doing.
Any one reader is doing one of the three; you are writing for all three at once, so the body MUST serve each of them and satisfying one is not a licence to drop another.
-
Reader 1 has decided to pick this up, and needs to understand the problem in enough detail to solve it. Your primary success metric is therefore whether this knowledge can be accurately and efficiently conveyed.
-
Reader 2 is checking whether this issue is what they're hitting right now — usually a bug. They are matching, not reading: an error string, a version or a triggering condition either matches theirs or it doesn't.
-
Reader 3 arrives after it closed, to find out why. A description that only parses alongside the comments has failed them, and so has an Open question nobody deleted.
Which path
A bug issue is an investigation log; a feature issue is a design brief. They draw different palette sections because one converges on a fact and the other on a choice.
- Fork on what the issue converges on, not on the label. "Queries got 10x slower" converges on a fact — bug. "Make queries faster" converges on a choice — feature. Evaluation criteria and prior art are dead weight where there is a correct answer; symptoms and root cause are dead weight where nothing is broken.
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 Changed · +7 lines 1b22b29590ba
- 1mo ago Changed · -30 lines a7b084c2e494
- 1mo ago Changed · +57 lines c5b044604769
- 1mo ago Changed · +1 lines 6c9dacd52fee
- 1mo ago Changed · +66 lines · +7 tokens per session 25641940fb5b
- 1mo ago Changed · +10 lines b61a1433af0b
- 1mo ago First seen · 122 lines · 134 tokens per session scan A 5d5d33feb92f
issue is a skill published in the GitHub repository juxt/claude-plugins (10 stars, last pushed yesterday), licensed MIT. It adds 141 tokens to every session and 3,340 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…
implement-issue
Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.