blazemeter-getting-started

blazemeter-getting-started is a skill for Claude Code, Codex from Blazemeter/bzm-mcp. It costs 96 tokens per session (1,022 once invoked), scanned A, original, Apache-2.0.

An introduction to BlazeMeter, a software testing platform, for new users and people moving from other testing tools.

In plain words
What is it for?
Use it to learn BlazeMeter, migrate from Runscope or JMeter, understand its glossary, explore accounts and workspaces, or test mobile websites and apps.
Why use it?
It explains the platform’s terminology, onboarding path, migration options, and basic structure before you start using it.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to learn BlazeMeter, migrate from Runscope or JMeter, understand its glossary, explore accounts and workspaces, or test mobile websites and apps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/blazemeter/bzm-mcp/blazemeter-getting-started
Install

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.

Any agent
npx skills add Blazemeter/bzm-mcp --skill blazemeter-getting-started
Clone the repo
git clone --depth 1 https://github.com/Blazemeter/bzm-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for blazemeter-getting-started

README.md
[![agentmods](https://agentmods.dev/badge/skills/blazemeter/bzm-mcp/blazemeter-getting-started.svg)](https://agentmods.dev/skills/blazemeter/bzm-mcp/blazemeter-getting-started)
Your own site
<a href="https://agentmods.dev/skills/blazemeter/bzm-mcp/blazemeter-getting-started"><img src="https://agentmods.dev/badge/skills/blazemeter/bzm-mcp/blazemeter-getting-started.svg" alt="Measured on agentmods" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,022 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00096 $0.01022
Opus 5 $0.00048 $0.00511
Sonnet 5 $0.00019 $0.00204
Haiku 4.5 $0.00010 $0.00102

Measured 8d ago against content hash d8bee545d474, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

blazemeter-getting-started 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 8d 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.

resources/skills/blazemeter-getting-started/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

BlazeMeter Getting Started

Getting started guides and resources for new BlazeMeter users.

Overview

Getting Started covers onboarding, migration guides, terminology, and mobile testing. This skill helps new users understand BlazeMeter and transition from other tools.

Quick Start

  1. Onboarding: Navigate BlazeMeter University
  2. Migration: Transition from Runscope or JMeter
  3. Journey: Understand the continuous testing journey
  4. Glossary: Reference BlazeMeter terminology
  5. Mobile: Test mobile sites and apps

MCP Tools Integration

Getting started with BlazeMeter involves understanding the platform structure. You can use BlazeMeter MCP tools to explore your account, workspaces, and projects:

Available MCP Tools

  • User Information:

    • blazemeter_user with action read_user - Read current user information
    • Returns: User details including default account, workspace, and project
  • Account Exploration:

    • blazemeter_account with action read - Read account information
    • blazemeter_account with action list - List all accessible accounts
    • Required args: account_id (integer) for read action
  • Workspace Exploration:

    • blazemeter_workspaces with action read - Read workspace details
    • blazemeter_workspaces with action list - List all workspaces in an account
    • Required args: workspace_id (integer) for read action, account_id (integer) for list action
  • Project Exploration:

    • blazemeter_project with action read - Read project information
    • blazemeter_project with action list - List all projects in a workspace
    • Required args: project_id (integer) for read action, workspace_id (integer) for list action

When to Use MCP Tools

  • Account Setup: Explore your account structure when getting started
  • Workspace Navigation: Understand workspace organization
  • Project Discovery: Discover existing projects and tests
  • Learning: Use tools to learn about BlazeMeter structure

Read the full file on GitHub · 91 lines

Files

What ships with it

6 files beside SKILL.md 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.

Changes

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.

  1. 8d ago First seen · 91 lines · 96 tokens per session scan A d8bee545d474

Subscribe to this mod's changes

blazemeter-getting-started is a skill published in the GitHub repository Blazemeter/bzm-mcp (26 stars, last pushed today), licensed Apache-2.0. It adds 96 tokens to every session and 1,022 once invoked, about $0.0005 per session on Opus 5. 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-30.

Related

Other skills, from other repositories

load-testing-expert

Expert in performance and load testing using JMeter, k6, Gatling, load patterns, metrics analysis, and performance optimization. Use when the user mentions performance, testing, QA, scalability, performance testing, or JMeter, or when the task involves Load Testing Types, Key Metrics, Tools & Frameworks, or k6 Load…

personamanagmentlayer/pcl · 75 tokens

mk-qa-master

Run, generate, debug, and improve software tests through mk-qa-master's MCP tools (pytest / Playwright / Jest / Cypress / Maestro / Schemathesis / Newman) and its v0.7 AI Visual Challenge Solver (reCAPTCHA / hCaptcha) and v0.8 OWASP API Security Top 10 scanner. Use when the user asks to run their test suite, diagnose…

kao273183/mk-qa-master · 172 tokens

windows-test-truth

Diagnose Windows test runs that lie — os error 4551 means the binary never executed, and a workspace test total can silently lose every suite after a blocked one. Use when cargo test reports a failure with no failing test named, when a test count looks lower than expected on Windows, or when a freshly built binary…

AURORA-NEURO/aurora-agent · 77 tokens

discriminating-experiment-design

Recognize when a benchmark cannot discriminate between methods, construct experiment families that could, sweep structural knobs without sweeping the decision itself, and report a tie that survives as the headline result. Use when all methods score the same on your benchmark, when designing a new evaluation world or…

AURORA-NEURO/aurora-agent · 89 tokens

equal-engineering-baselines

Build and tune baselines with the same engineering effort as the system under test, rank them on admissibility rather than on getting the right answer, and render refusals as refusals rather than zeros. Use when writing or reviewing any benchmark or comparison table, when a baseline looks suspiciously weak, when a…

AURORA-NEURO/aurora-agent · 95 tokens

metamorphic-evaluation

Grow an evaluation suite by mutation with executable postconditions, count effective diversity in equivalence classes rather than instances, and report yield honestly. Use when generating benchmark variants or augmented test cases, when a suite's instance count is quoted as evidence of coverage, when checking whether…

AURORA-NEURO/aurora-agent · 81 tokens