Borrowing it
Nothing to install: this file belongs to MadaBurns/bv-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MadaBurns/bv-mcp/main/.claude/skills/bv-mcp-testing/SKILL.mdgit clone --depth 1 https://github.com/MadaBurns/bv-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/madaburns/bv-mcp/bv-mcp-testing)<a href="https://agentmods.dev/skills/madaburns/bv-mcp/bv-mcp-testing"><img src="https://agentmods.dev/badge/skills/madaburns/bv-mcp/bv-mcp-testing/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/madaburns/bv-mcp/bv-mcp-testing"><img src="https://agentmods.dev/badge/skills/madaburns/bv-mcp/bv-mcp-testing.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.00181 | $0.01938 |
| Opus 5 | $0.00090 | $0.00969 |
| Sonnet 5 | $0.00036 | $0.00388 |
| Haiku 4.5 | $0.00018 | $0.00194 |
Grade A, and why
bv-mcp-testing 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 82 lines · 181 tokens per session scan A 0460c5cec47f
bv-mcp-testing is a skill published in the GitHub repository MadaBurns/bv-mcp (9 stars, last pushed today), with no licence file. It adds 181 tokens to every session and 1,938 once invoked, about $0.0009 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-31.
Other skills, from other repositories
deepeval
Use when discussing or working with DeepEval (the python AI evaluation framework).
AI & LLM Security
LLM and AI application security testing — prompt injection, jailbreak resistance, OWASP LLM Top 10 (2025), RAG and agent/tool-use security, model supply chain, and AI red teaming for authorized assessments.
iterative-refinement
Disciplined, measurable iteration for a substantial refinement or investigation: loop against verifiable pass/fail conditions, fan work out to subagents, and keep the main context lean. Use when improving something measurable over repeated cycles (tuning a metric or detector, refactoring against a regression bar)…
verify-changes
Verify code changes by running the project's typecheck, build, lint, and targeted tests, then fix and re-run until clean. Use after editing any source file.
chimera-prove-the-test-discriminates
A regression test you never saw fail is a guess. Re-break the code and watch it go red before you commit it.
chimera-test-the-wiring-not-the-class
A class assembled by hand in a test proves the class works, not that anything reaches it — cover the path production actually takes.