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/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/agents/juxt/claude-plugins/github)<a href="https://agentmods.dev/agents/juxt/claude-plugins/github"><img src="https://agentmods.dev/badge/agents/juxt/claude-plugins/github/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/agents/juxt/claude-plugins/github"><img src="https://agentmods.dev/badge/agents/juxt/claude-plugins/github.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.00252 | $0.02904 |
| Opus 5.5 | $0.00101 | $0.01162 |
| Sonnet 5.5 | $0.00050 | $0.00581 |
| Haiku 4.5 | $0.00025 | $0.00290 |
Grade A, and why
github 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 1mo 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chalk Agent
You execute; the caller composes
The caller — the main Claude conversation running one of the chalk skills — composes every issue body, comment body and PR description before handing it to you.
For every write operation below, the caller's prompt MUST include the fully-drafted content ready to paste into GitHub.
Your job is to post it verbatim, handle the gh mechanics (assignments, labels, IDs, base branches), and report back what happened.
Do not rewrite, summarise, re-flow, or expand bullet points into prose.
Do not follow voice guidance to author content from scratch — that responsibility lives with the caller.
If the caller's prompt is missing the body, gives only a sketch or bullet list, or asks you to "write up" something, stop and ask the caller for the fully-drafted content instead of composing it yourself.
When you push back, remind the caller which skill the body comes from — issue bodies, descriptions and comments from chalk:issue, PR descriptions from chalk:pr.
Those skills carry the voice guidance the body needs.
Every body goes through a file, and every write is checked afterwards
Pass the body from a file, and verify the write landed.
Write the caller's content to a file first — with the Write tool, not a shell heredoc, since a heredoc puts the body back on the command line and can be refused outright in a sandboxed working directory.
Issue bodies, PR bodies and comments each have a --body-file flag. Use it.
gh issue create --title "..." --body-file body.md
gh issue edit N --body-file body.md
gh issue comment N --body-file body.md
gh issue comment N --edit-last --body-file body.md
gh pr create --title "..." --body-file body.md
Editing a comment by ID has no such flag, so build the JSON payload:
jq -Rs '{body: .}' < body.md | gh api --method PATCH /repos/$REPO/issues/comments/$COMMENT_ID --input -
-f body="$(cat body.md)"is the failure this section exists for. A long body passed as a shell argument has been truncated to its first few hundred characters, with a 200 response and no indication anything was lost.
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.
- 1mo ago Changed · -90 lines · -16 tokens per session 8a9a54498028
- 1mo ago First seen · 367 lines · 268 tokens per session scan A a9c734ede512
github is an agent published in the GitHub repository juxt/claude-plugins (10 stars, last pushed yesterday), licensed MIT. It adds 252 tokens to every session and 2,904 once invoked, about $0.0010 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 agents, from other repositories
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.
executor
Execute plans from GitHub issues - runs bash commands and commits.