shiploop

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

shiploop 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/plugin.json · 29 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "shiploop",
  "displayName": "shiploop",
  "version": "1.17.2",
  "description": "Self-improving multi-agent harness that grinds your ticket backlog across every repo in your product — guarded auto-merge on green CI, and every resolved ticket writes a lesson into your git-tracked CLAUDE.md. Every ticket starts on a cheap tier and escalates once, on measured failure, instead of being predicted expensive up front; deterministic fixes skip the model entirely; and the lessons file evicts rather than accumulates, so always-on context stays a fixed budget.",
  "author": {
    "name": "anshss",
    "url": "https://github.com/anshss"
  },
  "homepage": "https://github.com/anshss/shiploop",
  "repository": "https://github.com/anshss/shiploop",
  "license": "Apache-2.0",
  "keywords": [
    "self-improving",
    "multi-agent",
    "orchestration",
    "model-routing",
    "backlog",
    "monorepo",
    "multi-repo",
    "worktrees",
    "autonomous-agent",
    "ticket-queue",
    "governor",
    "headless-worker"
  ]
}

Files

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.

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