ran

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.

Security

Grade A, and why

ran 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 yesterday.

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.

.claude-plugin/marketplace.json · 26 lines

What it actually says

{
  "name": "ran",
  "owner": {
    "name": "chaxus",
    "url": "https://github.com/chaxus/ran"
  },
  "description": "Skills for the ran monorepo libraries — ranui (web components) and ranuts (utilities) — so AI can read and use them without spelunking the source. Install whichever you use.",
  "metadata": {
    "pluginRoot": "./plugins"
  },
  "plugins": [
    {
      "name": "ranui",
      "source": "./plugins/ranui",
      "description": "ranui web-component library: import map, element inventory, builder/reactivity, accessibility, conventions.",
      "author": { "name": "chaxus" }
    },
    {
      "name": "ranuts",
      "source": "./plugins/ranuts",
      "description": "ranuts utility library: import map (utils/node/visual/vnode), ranuts/utils inventory, conventions.",
      "author": { "name": "chaxus" }
    }
  ]
}

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.

Related

Other plugins, from other repositories