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 v0idOS/performance-deitynpx agentmods add plugins/v0idos/performance-deity/performance-deitygit clone --depth 1 https://github.com/v0idOS/performance-deityGrade A, and why
performance-deity 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": "performance-deity",
"description": "Nine benchmark-driven performance engineering skills for Claude Code. Adds CPU optimization, memory leak detection, race condition testing, database query analysis, chaos engineering, network payload reduction, CI/CD acceleration, telemetry instrumentation, and UI frame-rate enforcement.",
"author": {
"name": "v0idOS"
},
"homepage": "https://v0idOS.github.io/performance-deity",
"repository": "https://github.com/v0idOS/performance-deity",
"license": "MIT",
"keywords": [
"performance",
"optimization",
"benchmarking",
"memory-leak",
"concurrency",
"database",
"stress-test",
"telemetry",
"ui"
],
"skills": "./skills"
}
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.
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 · 23 lines scan A 64551db5cbe0
performance-deity is a plugin published in the GitHub repository v0idOS/performance-deity (2 stars, last pushed 4mo 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
vukkt-plugins
Plugins by Vuk Topalovic — currently token-warden, a measurement and selection layer that makes Claude Code subagents measurably cheaper over time.
token-warden
Agent memory, charged rent. A Stop hook records what each session costs; expensive runs are distilled into candidate efficiency rules; each candidate is benchmarked on a frozen golden suite and kept only if it saves at least twice its context rent. Six commands. Two theorems survived measurement and three were deleted.
skill-creator-plus-marketplace
Plugin marketplace listing 1 plugin: skill-creator-plus.
skill-creator-plus
Create, test, evaluate, and iteratively improve Claude Code skills with built-in benchmarking, blind A/B comparison, and description optimization.
widget-fixture
Fixture plugin exercising the script-invocation stanzas in assets/. Not shipped; harness only.
autoresearch-marketplace
Autonomous experiment loops for Claude Code — edit, measure, keep or discard, repeat forever.