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.
git clone --depth 1 https://github.com/v0idOS/performance-deityWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/v0idos/performance-deity/performance-deity)<a href="https://agentmods.dev/plugins/v0idos/performance-deity/performance-deity"><img src="https://agentmods.dev/badge/plugins/v0idos/performance-deity/performance-deity/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/v0idos/performance-deity/performance-deity"><img src="https://agentmods.dev/badge/plugins/v0idos/performance-deity/performance-deity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 1mo 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": "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 it installs
The manifest is a name and a version. 17 skills travel with it, and installing the plugin installs all of them — 268 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill memory A 33 tokens
- Skill telemetry A 37 tokens
- Skill performance-deity A 0 tokens
- Skill optimize A 34 tokens
- Skill concurrency A 28 tokens
- Skill concurrency-deity A 0 tokens
- Skill memory-deity A 0 tokens
- Skill stress-test A 34 tokens
- Skill ui A 36 tokens
- Skill database A 34 tokens
- Skill database-deity A 0 tokens
- Skill network A 32 tokens
- Skill stress-test-deity A 0 tokens
- Skill ui-deity A 0 tokens
- Skill build-deity A 0 tokens
- Skill network-deity A 0 tokens
- Skill telemetry-deity A 0 tokens
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.
- 1mo ago First seen · 23 lines scan A 64551db5cbe0
performance-deity is a plugin published in the GitHub repository v0idOS/performance-deity (2 stars, last pushed 5mo 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
technology
Architecture, engineering delivery, development discipline, debugging, review, and AI and automation systems.
sre-bot
SRE triage assistant for plain-English production health and Kubernetes questions in Slack. One pinned upstream Kubernetes MCP connector exposes the core toolset: reads execute immediately, six mutations require a fresh human approval, and unmatched tools fail closed. Kubernetes RBAC limits writes to disposable…
fuse-changelog
Claude Code update watcher: changelog tracking, breaking changes detection, community pulse via Exa, plugin compatibility analysis.
rubber-duck
Socratic debugging companion. Instead of giving the answer, asks one question at a time until you find it yourself.
karellen-lsp-mcp
LSP-backed code intelligence for Claude Code via MCP and native LSP - navigate definitions, references, call hierarchies, type hierarchies, and diagnostics across codebases.
craftsman
Ship something with Lovable, Replit, Bolt, v0, Claude Code, or Codex and it works, but nobody with an engineering background has checked it. This is the engineering review you'd get from the technical co-founder you don't have. craft-audit checks the whole project across ten areas: UX, frontend, backend, database…