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/plugins/juxt/claude-plugins/chalk)<a href="https://agentmods.dev/plugins/juxt/claude-plugins/chalk"><img src="https://agentmods.dev/badge/plugins/juxt/claude-plugins/chalk/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/plugins/juxt/claude-plugins/chalk"><img src="https://agentmods.dev/badge/plugins/juxt/claude-plugins/chalk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chalk 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 today.
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
{
"name": "chalk",
"version": "0.37.0",
"description": "Capture intent across issues, commits, and PRs — why, not just what"
}
What it installs
The manifest is a name and a version. 11 skills, 3 agents travel with it, and installing the plugin installs all of them — 1,567 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill voice A 73 tokens
- Skill commit A 98 tokens
- Skill issue A 141 tokens
- Skill code-comments A 90 tokens
- Skill pr A 130 tokens
- Skill explicate A 74 tokens
- Skill sitrep A 89 tokens
- Skill goal-tree A 101 tokens
- Skill pick-up A 72 tokens
- Skill rubber-duck A 96 tokens
- Skill put-down A 77 tokens
- Agent github A 252 tokens
- Agent weed-prose A 134 tokens
- Agent weed-comments A 140 tokens
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.
- today Changed b193c566e95a
- 3d ago Changed 89b276791bf6
- 4d ago Changed d46fd3aef397
- 8d ago Changed 82c36b3f724a
- 11d ago Changed 95ddb455bbb5
- 13d ago Changed 64c32eb6d56f
- 1mo ago Changed e2bd672316a5
- 1mo ago Changed 985ea2ec6572
- 1mo ago Changed 4e2cb466f189
- 1mo ago First seen · 6 lines scan A 7c308895d560
chalk is a plugin published in the GitHub repository juxt/claude-plugins (10 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
fuse-rules
Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards.
lanes-bridges
Bridge Lanes with GitHub and Linear: import issues, batch-spawn a session per ticket, and post results back upstream. Split out of lanes-desktop in 0.7.0.
dev
Ralph Loop development lifecycle: ticket assignment through merge-ready PR. Includes start, code, pr, poll, ci, backport, work, grill-with-docs, to-prd, to-issues, handoff, and qe.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
gh-cli
GitHub CLI integration with focused skills for pull requests, stacked pull requests, issues, GitHub Actions, and viewing GitHub file URLs.
tgc-skills
A shipping pipeline for Claude Code: orchestrate a locked plan with fresh-context agents, polish the diff, ship it to a reviewed PR, run an agent review-fix loop until clean, and clean up after merge.