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 raivisdejus/claude-code-pluginsnpx agentmods add plugins/raivisdejus/claude-code-plugins/marketplacegit clone --depth 1 https://github.com/raivisdejus/claude-code-pluginsGrade A, and why
screen-reader-plugins 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- screen-reader — 86% identical, 28 lines differ
What it actually says
{
"name": "screen-reader-plugins",
"owner": {
"name": "Raivis Dejus"
},
"metadata": {
"description": "Screen reader plugins for Claude Code",
"version": "1.0.0",
"pluginRoot": "./"
},
"plugins": [
{
"name": "screen-reader",
"source": "./screen-reader",
"description": "Announces Claude Code responses using screen readers (NVDA, JAWS, Orca, VoiceOver) for accessibility",
"version": "1.0.0",
"author": {
"name": "Raivis Dejus"
},
"repository": "https://github.com/RaivisDejus/claude-code-plugins",
"license": "MIT",
"keywords": ["accessibility", "screen-reader", "tts", "nvda", "jaws", "orca", "voiceover"],
"category": "accessibility"
}
]
}
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.
- 2d ago First seen · 27 lines scan A 5e2615ac9090
screen-reader-plugins is a plugin published in the GitHub repository raivisdejus/claude-code-plugins (6 stars, last pushed 7mo 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-31.
Other plugins, from other repositories
humanizer
Rewrite AI-sounding text so it reads naturally 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.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.