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-troubleshootinggit 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-troubleshooting)<a href="https://agentmods.dev/skills/blazemeter/bzm-mcp/blazemeter-troubleshooting"><img src="https://agentmods.dev/badge/skills/blazemeter/bzm-mcp/blazemeter-troubleshooting/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-troubleshooting"><img src="https://agentmods.dev/badge/skills/blazemeter/bzm-mcp/blazemeter-troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00131 | $0.00900 |
| Opus 5.5 | $0.00052 | $0.00360 |
| Sonnet 5.5 | $0.00026 | $0.00180 |
| Haiku 4.5 | $0.00013 | $0.00090 |
Grade A, and why
blazemeter-troubleshooting 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BlazeMeter Troubleshooting
Comprehensive troubleshooting guide for resolving issues in BlazeMeter.
Overview
This skill covers troubleshooting for API Monitoring, Performance Testing, general issues, integrations, and security. It includes diagnostic steps, common solutions, and support resources. Effective troubleshooting requires systematic diagnosis and understanding of common issues and their solutions.
Quick Start
- Identify the issue: Determine if it's API Monitoring, Performance Testing, or general
- Check relevant reference: Review the appropriate troubleshooting guide
- Apply solutions: Follow diagnostic steps and solutions
- Contact support: If issues persist, use support resources
MCP Tools Integration
While troubleshooting is primarily done through UI and logs, you can use BlazeMeter MCP tools to access test execution information and results that may help diagnose issues:
Available MCP Tools
-
Test Execution Information:
blazemeter_executionwith actionread- Read test execution details and statusblazemeter_executionwith actionlist- List all executions for a test- Required args:
execution_id(integer) ortest_id(integer) - Returns: Execution details including status, errors, and results
-
Test Information:
blazemeter_testswith actionread- Read test details and configuration- Required args:
test_id(integer) - Returns: Test details including configuration that may help identify issues
When to Use MCP Tools
- Execution Analysis: Use MCP tools to programmatically retrieve execution details and errors
- Automation: Integrate troubleshooting information into automation scripts
- Monitoring: Monitor test execution status and errors programmatically
Example Workflow
Getting Execution Details for Troubleshooting:
- Use
blazemeter_executionwith actionlistto get execution IDs for a test - Use
blazemeter_executionwith actionreadto get detailed execution information - Review execution status, errors, and results to identify issues
- Use this information to diagnose and resolve problems
What ships with it
5 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.
- 1mo ago First seen · 77 lines · 131 tokens per session scan A 824ac7b980b0
blazemeter-troubleshooting is a skill published in the GitHub repository Blazemeter/bzm-mcp (26 stars, last pushed 20d ago), licensed Apache-2.0. It adds 131 tokens to every session and 900 once invoked, about $0.0005 per session on Opus 5.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
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…
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
opik-explain
Root-cause a specific Opik trace, or a pattern across traces, and return a grounded explanation. Uses the hosted Opik MCP when it is connected, and falls back to SDK scripting otherwise. Returns the root cause, the evidence spans as clickable Opik UI links, and one suggested next step. Use for "why did this trace…
opik-compare
Run a candidate against the baseline over an Opik test suite and read the numbers back — which cases broke, which got fixed, the per-metric deltas, worst rows, and whether the two runs are comparable — with the Opik compare-view link. Runs via the SDK; reads results via the MCP when connected. Does not issue a…
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
opik-verify
Decide ship or hold for a candidate from the compare skill's numbers, against an explicit release policy — regressions, pass rate, safety-tagged cases, subgroup consistency, latency and cost budgets, flakiness, evidence size, and whether the judge is validated. Reads two experiments on an Opik test suite via the SDK…