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 score-technologies/score-studio-agent-pluginsnpx agentmods add plugins/score-technologies/score-studio-agent-plugins/score-studiogit clone --depth 1 https://github.com/score-technologies/score-studio-agent-pluginsGrade A, and why
score-studio 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.
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": "score-studio",
"version": "0.2.0",
"description": "Operate evidence-gated computer-vision workflows in Score Studio.",
"author": {
"name": "Score Technologies",
"url": "https://github.com/score-technologies"
},
"homepage": "https://github.com/score-technologies/score-studio-agent-plugins",
"repository": "https://github.com/score-technologies/score-studio-agent-plugins",
"license": "Apache-2.0",
"keywords": ["computer-vision", "evaluation", "deployment", "mcp"]
}
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.
- yesterday First seen · 14 lines scan A 665f3663dc0e
score-studio is a plugin published in the GitHub repository score-technologies/score-studio-agent-plugins (0 stars, last pushed 7d ago), licensed Apache-2.0. 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
horizon-shield
Audit Japanese construction and renovation estimates against the open JCCDB dataset and return Bitcoin-anchored, independently recomputable fair-price receipts. Read-only remote MCP, no API key. Adds /audit, /red-flags, /verify commands.
the-horizons
Plugin marketplace listing 1 plugin: horizon-shield.
python-code-validator
Checks every Python file Claude writes, before you read it: syntax, lint, types, an AST security policy and a credential scan, with the exact fix when there is one.
statemind
Plugin marketplace listing 1 plugin: python-code-validator.
turnale
Run recreational racket-sport tournaments from chat: fair draws, live standings, score entry, dropout handling. Bundles the Turnale MCP connector and a tournament-organiser skill.
turnale
Plugin marketplace listing 1 plugin: turnale.