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 synaptixs/spinenpx agentmods add plugins/synaptixs/spine/marketplacegit clone --depth 1 https://github.com/synaptixs/spineGrade A, and why
spine 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.
What it actually says
{
"name": "spine",
"owner": {
"name": "Synaptixs",
"url": "https://github.com/synaptixs/spine"
},
"description": "Spine's Claude Code plugin marketplace — delegate a ticket, get a reviewed PR.",
"plugins": [
{
"name": "spine",
"source": "./plugins/spine",
"description": "Understand any codebase, then ship changes to it. Read-only comprehension tools hand you engineering decisions (what breaks if you change X, what's untested, where a ticket lands) from a deterministic Product Knowledge Graph — across one repository or several. Then delegate a ticket and, on confirm, get a reviewed, tested PR. Greenfield + brownfield across Python, Java, TypeScript, C#, C, C++, Go, and SQL, exposed as MCP tools + an understand-codebase skill.",
"version": "3.25.1",
"category": "Engineering",
"keywords": [
"sdlc",
"codegen",
"mcp",
"knowledge-graph",
"greenfield",
"brownfield",
"pkg",
"multi-repo"
]
}
]
}
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 · 28 lines scan A 5e531098e4e5
spine is a plugin published in the GitHub repository synaptixs/spine (8 stars, last pushed 4d 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
ganvil
Long-running autonomous coding harness with Planner-Generator-Evaluator architecture and Sprint decomposition. Builds complete applications from simple descriptions.
ganvil
Plugin marketplace listing 1 plugin: ganvil.
jenkins-cli
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.
axint
Compile TypeScript intent definitions into native Apple App Intents and MCP tool servers. Define once, ship to Siri, Shortcuts, and Spotlight.
polisade-marketplace
Plugin marketplace listing 1 plugin: polisade.
spec-first
Spec-first development: define a spec, implement it, and generate docs.