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.
npx skills add Blazemeter/bzm-mcp --skill blazemeter-recordersgit clone --depth 1 https://github.com/Blazemeter/bzm-mcpWrote 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/skills/blazemeter/bzm-mcp/blazemeter-recorders)<a href="https://agentmods.dev/skills/blazemeter/bzm-mcp/blazemeter-recorders"><img src="https://agentmods.dev/badge/skills/blazemeter/bzm-mcp/blazemeter-recorders/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/skills/blazemeter/bzm-mcp/blazemeter-recorders"><img src="https://agentmods.dev/badge/skills/blazemeter/bzm-mcp/blazemeter-recorders.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00076 | $0.00680 |
| Opus 5 | $0.00038 | $0.00340 |
| Sonnet 5 | $0.00015 | $0.00136 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade A, and why
blazemeter-recorders 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BlazeMeter Recorders
Comprehensive guide for recording performance and functional tests in BlazeMeter.
Overview
BlazeMeter provides two main recording options: Chrome Extension for browser-based recording and Proxy Recorder for mobile and web app recording. This skill covers both recording methods and their configuration.
Quick Start
- Chrome Extension: Record tests directly from Chrome browser
- Proxy Recorder: Record mobile and web app traffic via proxy
- Configuration: Configure browsers and devices for proxy recording
MCP Tools Integration
While recording is primarily done through browser extensions and proxy configuration, you can use BlazeMeter MCP tools to manage tests created from recordings:
Available MCP Tools
-
Test Management:
blazemeter_testswith actionread- Read test details for tests created from recordingsblazemeter_testswith actionlist- List all tests in a project, including recorded tests- Required args:
test_id(integer) orproject_id(integer) - Returns: Test details including configuration and scripts
-
Test Execution:
blazemeter_executionwith actionread- Read execution details for recorded testsblazemeter_executionwith actionlist- List all executions for a recorded test- Required args:
execution_id(integer) ortest_id(integer) - Returns: Execution details and results
When to Use MCP Tools
- Test Management: Manage tests created from recordings programmatically
- Execution Monitoring: Monitor execution of recorded tests
- Automation: Integrate recorded tests into automation workflows
Example Workflow
Managing Recorded Tests:
- Record test using Chrome Extension or Proxy Recorder
- Export recorded script to BlazeMeter
- Use
blazemeter_testswith actionlistto find the created test - Use
blazemeter_testswith actionreadto get test details - Use
blazemeter_executionto monitor test execution
What ships with it
2 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.
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.
- 10d ago First seen · 66 lines · 76 tokens per session scan A 27b0d92f2f6a
blazemeter-recorders is a skill published in the GitHub repository Blazemeter/bzm-mcp (26 stars, last pushed yesterday), licensed Apache-2.0. It adds 76 tokens to every session and 680 once invoked, about $0.0004 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.
Other skills, from other repositories
tabnexus-mcp-evals
Generate, validate, and run isolated Codex-to-TabNexus MCP evaluations with a curated 600-query dataset, executable gold tool labels, safety checks, and best-of-three stability scoring. Use when testing TabNexus MCP tool coverage, Agent behavior, regression quality, destructive-action safety, prompt changes, or a…
browser-automation
This skill should be used when the user asks about browser automation, testing web pages, extracting content, filling forms, taking screenshots, or monitoring console/network activity. Activates for E2E testing, form automation, browsing tasks, or debugging web applications.
qa-runner
Use when asked to "run QA", "qa check", "test checklist", or execute QA checklists against a running app via browser automation. Requires the browser-bridge MCP server and Chrome extension.
qa-use
E2E testing and browser automation with qa-use CLI. Use when the user needs to run tests, verify features, automate browser interactions, or debug test failures.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
pursr
Use Pursr for browser screenshots, scripted visual operation, visual regression, accessibility audits, DOM inspection, and MCP-driven browser sessions. Use when a user asks an agent to inspect a site, operate an existing browser session, fill or draft UI content, record a tutorial, compare visuals, debug layout, or…