Borrowing it
Nothing to install: this file belongs to FlorianBruniaux/google-search-console-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/FlorianBruniaux/google-search-console-mcp/main/.claude/commands/run-tests.mdgit clone --depth 1 https://github.com/FlorianBruniaux/google-search-console-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/commands/florianbruniaux/google-search-console-mcp/run-tests)<a href="https://agentmods.dev/commands/florianbruniaux/google-search-console-mcp/run-tests"><img src="https://agentmods.dev/badge/commands/florianbruniaux/google-search-console-mcp/run-tests/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/commands/florianbruniaux/google-search-console-mcp/run-tests"><img src="https://agentmods.dev/badge/commands/florianbruniaux/google-search-console-mcp/run-tests.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.00027 | $0.00478 |
| Opus 5 | $0.00014 | $0.00239 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
run-tests 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 9d 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.
What it actually says
Run Tests
Run the pytest suite for gsc-mcp, with optional module filter.
Usage
/run-tests # All tests
/run-tests analytics # Only tests/test_analytics.py
/run-tests ga4 # Only tests/test_ga4.py
Steps
-
Parse
$ARGUMENTSfor optional module name -
Run the appropriate command:
# All tests, quiet output
.venv/bin/pytest tests/ -q
# Single module, verbose
.venv/bin/pytest tests/test_<module>.py -v
# Filter by test name
.venv/bin/pytest tests/ -k "test_batch" -v
- Report the result:
- Total: passed / failed / skipped counts
- On failures: exact assertion message and file:line for each failure
- On all pass: confirm with the test count
On Failure
For each failing test, diagnose before suggesting a fix.
Wrong patch path: patch("gsc_mcp.auth.get_searchconsole_service") fails because the mock doesn't reach the call site. Fix is to patch at the module that imports the function, e.g. gsc_mcp.tools.analytics.get_searchconsole_service.
Missing GA4 fixture: GA4_PROPERTY_ID not set in test environment. Fix is to add monkeypatch.setenv("GA4_PROPERTY_ID", "123456789") in an autouse fixture (see tests/test_ga4.py).
httpx context manager not wired: AttributeError: __enter__ on the mock. Fix is to set mock_client.__enter__ = MagicMock(return_value=mock_client) and mock_client.__exit__ = MagicMock(return_value=False).
sitemap_audit double mock: this tool patches both httpx.Client and get_search_analytics. Patching only one of them leaves the other calling the real implementation.
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.
- 9d ago First seen · 51 lines · 27 tokens per session scan A e3661cb8e708
run-tests is a command published in the GitHub repository FlorianBruniaux/google-search-console-mcp (10 stars, last pushed 8d ago), licensed MIT. It adds 27 tokens to every session and 478 once invoked, about $0.0001 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 commands, from other repositories
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
timeout-fix
A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…