Agent Plugins Marketplace
← All plugins

vc-perf

v0.3.0

Three-layer performance loop for Virto Commerce — BenchmarkDotNet A/B (L1) → k6 load harness (L2) → dotnet-trace allocation/CPU/DB attribution (L3), a machine-readable perf-verdict, and optimization PRs. Depends on vc-fix: it REUSES vc-fix's onboarding (/project-init, project-profile.json), fix routing (qa-fix-routing), the backend developer/reviewer agents, and dotnet-fix — and ships ONLY the perf-specific measurement delta (no duplication of vc-fix machinery). Advisory only, never a CI gate.

Claude Code4 Skills

By Virto CommerceLicense: TBD-internal2 GitHub starsUpdated 1 hour ago

Directory evidence

Runtimes
Claude Code
Parsed components
4 skill or MCP entries
Source updated
Sep 24, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install vc-perf for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install vc-perf@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/VirtoCommerce/vc-mcp-testing-module

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/vc-perf/.

Plugin files

plugins/vc-perf/
├── .claude-plugin/plugin.json
├── skills/perf-benchmark/SKILL.md
├── skills/perf-loadtest/SKILL.md
├── skills/perf-loop/SKILL.md
└── skills/perf-trace/SKILL.md

Included Skills4

perf-benchmarkskills/perf-benchmark/SKILL.md

Run VirtoCommerce x-module BenchmarkDotNet suites (the XAPI targets configured in perf.benchmark.xapiTargets) and turn two runs into a machine-readable performance verdict. Use to check whether a change regressed allocations or time across two revisions of this module's own source, between this module's override and the upstream stock path, or across an upstream before/after. Advisory only — never a CI gate.

perf-loadtestskills/perf-loadtest/SKILL.md

Run the L2 k6 load harness against the live Aspire-hosted backend and produce a summary + optional dotnet-counters CSV. Use to answer "how does the running system behave under load" — throughput, p95 latency, GC pressure — as opposed to L1 (BenchmarkDotNet, code-level) or L3 (dotnet-trace, attribution).

perf-loopskills/perf-loop/SKILL.md

Orchestrates the three-layer performance loop (bench → load → diagnose → optimize → verify) on the local Aspire-hosted backend. Use when the user asks to "run the perf loop", "load test X", "profile the backend", "where do the allocations come from", "why is this operation slow", or to verify a performance fix end-to-end. Routes to the right layer and tool; does not duplicate them. For pure BenchmarkDotNet before/after comparison use `perf-benchmark` directly.

perf-traceskills/perf-trace/SKILL.md

Capture a dotnet-trace / dotnet-counters session against the live backend and parse it with perftools (allocparse/cpuparse/dbparse) to attribute WHO is responsible for what L2 observed. Use when you know load behaves a certain way (L2) and need to find the responsible code — allocation churn, on-CPU time, or DB command shape.

Plugin manifests1

plugins/vc-perf/.claude-plugin/plugin.json
{
  "name": "vc-perf",
  "description": "Three-layer performance loop for Virto Commerce — BenchmarkDotNet A/B (L1) → k6 load harness (L2) → dotnet-trace allocation/CPU/DB attribution (L3), a machine-readable perf-verdict, and optimization PRs. Depends on vc-fix: it REUSES vc-fix's onboarding (/project-init, project-profile.json), fix routing (qa-fix-routing), the backend developer/reviewer agents, and dotnet-fix — and ships ONLY the perf-specific measurement delta (no duplication of vc-fix machinery). Advisory only, never a CI gate.",
  "version": "0.3.0",
  "displayName": "Virto Commerce Performance Loop",
  "author": {
    "name": "Virto Commerce",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/VirtoCommerce/vc-mcp-testing-module",
  "repository": "https://github.com/VirtoCommerce/vc-mcp-testing-module",
  "license": "TBD-internal",
  "keywords": [
    "performance",
    "benchmark",
    "load-test",
    "profiling",
    "virtocommerce",
    "perf"
  ],
  "defaultEnabled": false,
  "dependencies": [
    {
      "name": "vc-fix",
      "version": ">=0.7.0"
    }
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[vc-perf on Agent Plugins Marketplace](https://pluginsmp.com/plugins/vc-perf)