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/marketplace)<a href="https://agentmods.dev/plugins/juxt/claude-plugins/marketplace"><img src="https://agentmods.dev/badge/plugins/juxt/claude-plugins/marketplace/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/marketplace"><img src="https://agentmods.dev/badge/plugins/juxt/claude-plugins/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
juxt-plugins marketplace 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 7d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "juxt-plugins",
"owner": {
"name": "JUXT Ltd",
"email": "[email protected]"
},
"metadata": {
"description": "JUXT plugin marketplace for Claude Code",
"version": "1.0.0"
},
"plugins": [
{
"name": "a-star",
"description": "Agentic coding harness for complex domains: a cheap agent finds the route to the goal end-to-end, then each change lands small and simple enough for a human to review and put down.",
"source": "./plugins/a-star"
},
{
"name": "allium",
"description": "Velocity through clarity.",
"source": "./plugins/allium"
},
{
"name": "chalk",
"description": "Capture intent across issues, commits, and PRs — why, not just what.",
"source": "./plugins/chalk"
},
{
"name": "chill",
"description": "Interrupt forward momentum and step back to reassess. A circuit-breaker for when Claude is spinning or scope-creeping.",
"source": "./plugins/chill"
},
{
"name": "clojure-lsp",
"description": "Clojure / ClojureScript language server (clojure-lsp + clj-kondo) for code intelligence, refactoring, and analysis.",
"version": "1.0.0",
"source": "./plugins/clojure-lsp",
"category": "development",
"strict": false,
"lspServers": {
"clojure-lsp": {
"command": "clojure-lsp",
"extensionToLanguage": {
".clj": "clojure",
".cljs": "clojure",
".cljc": "clojure",
".edn": "clojure",
".bb": "clojure"
},
"startupTimeout": 120000
}
}
},
{
"name": "code-map",
"description": "Build and query a code-only LSP-based symbol and call-graph map of the current project. A navigation accelerator for multi-file code reasoning.",
"source": "./plugins/code-map"
},
{
"name": "glance",
"description": "Pipe long command output through glance for token-efficient summaThe plugins it lists here
This marketplace lists 5 plugins kept in the same repository. Each has its own page, its own measurements and its own install command.
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.
- 7d ago Changed 93534c49b027
- 11d ago Changed · -3 lines c3606999237a
- 13d ago Changed · +8 lines 0f2bf35d462d
- 1mo ago First seen · 67 lines scan A 780502e64034
juxt-plugins marketplace 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
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
themes-example
themes-example. An open-source AI agent that brings the power of Gemini directly into your terminal.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins marketplace
Plugin marketplace listing 123 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
code-modernization
Guided modernization for any legacy codebase: start with /modernize, get an assessment, an interactive map, the business rules mined from the code, and a plan you approve, then an upgrade, a rewrite or a rebuild with independent proof that the new code behaves like the old. Includes security hardening, a one-page…