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 withoneai/one-agent-plugin --skill blaze-meter-service-virtualizationgit clone --depth 1 https://github.com/withoneai/one-agent-pluginWrote 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/withoneai/one-agent-plugin/blaze-meter-service-virtualization)<a href="https://agentmods.dev/skills/withoneai/one-agent-plugin/blaze-meter-service-virtualization"><img src="https://agentmods.dev/badge/skills/withoneai/one-agent-plugin/blaze-meter-service-virtualization.svg" alt="Measured on agentmods" 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.00135 | $0.03912 |
| Opus 5 | $0.00068 | $0.01956 |
| Sonnet 5 | $0.00027 | $0.00782 |
| Haiku 4.5 | $0.00014 | $0.00391 |
Grade A, and why
blaze-meter-service-virtualization 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 4d 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.
This is a copy
78% identical to 2-chat — 237 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BlazeMeter Service Virtualization through One
BlazeMeter is a testing platform for web and API applications, and its Service Virtualization API enables developers to programmatically create and manage virtual services that simulate APIs and system dependencies for testing when real services are unavailable.
One exposes BlazeMeter Service Virtualization through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.
How to run an action
- Find the action in the table below, or call
search_one_platform_actionswith platformblaze-meter-service-virtualizationif it is not listed. - Call
get_one_action_knowledgewith the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters. - Call
execute_one_actionwith parameters copied from that knowledge.
Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.
Before you start
Call list_one_integrations once and confirm BlazeMeter Service Virtualization is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.
Each connection carries an access field. If it reports {"policy": "methods", "methods": ["GET"]} the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.
Before a write
Creates, updates, deletes and sends land on a real BlazeMeter Service Virtualization account and cannot be recalled. State the action and the specific target in one line before the first write in a task, and let the user stop you. Reads need no confirmation.
Actions
Tags
| Action | Method | Path | Action id |
|---|---|---|---|
| Get a Tag by ID | GET | /tags/{{tagId}} |
conn_mod_def::GJspyhTDryo::OivuzjHdRa6WrMpqXuF7JQ |
| Get a Tag by Name | GET | /tags/name/{{name}} |
conn_mod_def::GJspyo_XTbY::ln4xh3HhRZKLqXH28bTC2A |
| List Tags | GET | /tags |
conn_mod_def::GJspyZhp-gk::OwzorJsET-umeMIVdSmTnQ |
| Create a Tag | POST | /api/v1/tags |
conn_mod_def::GJspySwhmH0::5kIsqEs1TvKKGGnN1xoWQQ |
| Delete a Tag | DELETE | /tags/{{tagId}} |
conn_mod_def::GJspy4AZSC8::2WZnjklvRs26ctndvRQrag |
| Update a Tag | PUT | /tags/{{tagId}} |
conn_mod_def::GJspyxyPOqI::zPaSkB6jQ8iu7Sw3VoOlAg |
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.
- 4d ago First seen · 200 lines · 0 tokens per session scan A 72bc8c6f9fa5
blaze-meter-service-virtualization is a skill published in the GitHub repository withoneai/one-agent-plugin (1 stars, last pushed 19d ago), licensed MIT. It adds 135 tokens to every session and 3,912 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to 2-chat, differing in 237 lines, and is treated as a copy.
Other skills, from other repositories
dataset-evaluation
Validates dataset formatting and quality for SageMaker model fine-tuning (SFT, DPO, or RLVR). Use when the user says "is my dataset okay", "evaluate my data", "check my training data", "I have my own data", or before starting any fine-tuning job. Detects file format, checks schema compliance against the selected model…
uat-testing
Run end-to-end User Acceptance Tests for Agent Brain features. Builds wheels, installs packages, starts a test server, runs tests, and reports results — all without permission prompts.
gsd-add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
gsd-verify-work
Validate built features through conversational UAT.
gsd-audit-uat
Cross-phase audit of all outstanding UAT and verification items.