storj-plugins

A directory file that lists Claude Code plugins, including their names, descriptions, authors, categories, source locations, and homepages.

In plain words
What is it for?
It is for registering and describing developer and workflow plugins, including plugins hosted in a Git repository.
Why use it?
It gives a plugin system a structured catalogue of available add-ons and where to obtain them.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add storj/claude-plugins
agentmods
npx agentmods add plugins/storj/claude-plugins/marketplace
Clone the repo
git clone --depth 1 https://github.com/storj/claude-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

storj-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.

.claude-plugin/marketplace.json · 38 lines

What it actually says

{
  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  "name": "storj-plugins",
  "description": "Storj-managed directory of Claude Code plugins.",
  "owner": {
    "name": "Storj",
    "email": "[email protected]"
  },
  "plugins": [
    {
      "name": "storj-developer",
      "description": "Tools for Storj developers.",
      "author": {
        "name": "Storj",
        "email": "[email protected]"
      },
      "category": "development",
      "source": "./plugins/storj-developer",
      "homepage": "https://github.com/storj/claude-plugins"
    },
    {
      "name": "andrej-karpathy-skills",
      "description": "Behavioral guidelines to reduce common LLM coding mistakes: Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution.",
      "author": {
        "name": "forrestchang"
      },
      "category": "workflow",
      "source": {
        "source": "github",
        "repo": "multica-ai/andrej-karpathy-skills",
        "ref": "main",
        "sha": "2c606141936f1eeef17fa3043a72095b4765b9c2"
      },
      "homepage": "https://github.com/multica-ai/andrej-karpathy-skills"
    }
  ]
}
Changes

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.

  1. 2d ago First seen · 38 lines scan A 5e08b4c4c56d

Subscribe to this mod's changes

storj-plugins is a plugin published in the GitHub repository storj/claude-plugins (3 stars, last pushed 3mo 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.