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.
/plugin marketplace add K-dash/typemux-ccnpx agentmods add plugins/k-dash/typemux-cc/typemux-ccgit clone --depth 1 https://github.com/K-dash/typemux-ccGrade A, and why
typemux-cc 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 3d 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.
What it actually says
{
"name": "typemux-cc",
"version": "0.2.18",
"description": "Python type-checker LSP multiplexer for Claude Code (pyright, ty, pyrefly)",
"author": {
"name": "K-dash"
},
"homepage": "https://github.com/K-dash/typemux-cc",
"repository": "https://github.com/K-dash/typemux-cc",
"license": "MIT",
"keywords": ["lsp", "pyright", "ty", "pyrefly", "proxy", "rust", "monorepo", "python"],
"hooks": "./hooks.json",
"lspServers": {
"typemux-cc": {
"command": "${CLAUDE_PLUGIN_ROOT}/bin/typemux-cc",
"args": [],
"extensionToLanguage": {
".py": "python",
".pyi": "python"
}
}
}
}
What it installs
The manifest is a name and a version. 2 skills, 1 hook travel with it, and installing the plugin installs all of them — 114 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 24 lines scan A 86e39e1854b9
typemux-cc is a plugin published in the GitHub repository K-dash/typemux-cc (16 stars, last pushed 26d ago), 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-30.
Other plugins, from other repositories
python-lsp
Claude Code plugin for Python development with Pyright LSP integration, 15 automated hooks for type checking, linting (ruff), formatting (black), testing (pytest), and security scanning.
python-clean-architecture
Clean Architecture guidance for Python/FastAPI projects. Provides principles-driven design, Pythonic patterns, and layered architecture scaffolding based on Arjan Codes' methodology.
kolo
Kolo is a text-based Python debugger for AI agents. Capture every executed function, return value, local variable, HTTP request, and SQL query into greppable trace files.
modern-python
Modern Python best practices. Use when creating new Python projects, and writing Python scripts, or migrating existing projects from legacy tools.
modern-python
Modern Python best practices. Use when creating new Python projects, and writing Python scripts, or migrating existing projects from legacy tools.
grpc-python-best-practices
Python gRPC async-first Kubernetes-native best practices using grpc.aio — server bootstrap with graceful shutdown, shared per-process channel factory, canonical decorator pattern for cross-cutting concerns, maxconnectionage for HPA rebalancing, client-side LB via dns:/// + roundrobin over a headless Service (no se.