Borrowing it
Nothing to install: this file belongs to fruggr/zendesk-mcp-server. 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/fruggr/zendesk-mcp-server/main/.claude/skills/functional-testing/SKILL.mdgit clone --depth 1 https://github.com/fruggr/zendesk-mcp-serverWrote 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/fruggr/zendesk-mcp-server/functional-testing)<a href="https://agentmods.dev/skills/fruggr/zendesk-mcp-server/functional-testing"><img src="https://agentmods.dev/badge/skills/fruggr/zendesk-mcp-server/functional-testing.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.00083 | $0.01265 |
| Opus 5 | $0.00042 | $0.00633 |
| Sonnet 5 | $0.00017 | $0.00253 |
| Haiku 4.5 | $0.00008 | $0.00127 |
Grade A, and why
functional-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 6d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Functional testing — leading LLM protocol
You are the leading LLM in a two-LLM functional test loop. The other LLM runs locally on the user's machine (Claude Code CLI), executes scenarios against the real MCP server build, and pushes its artifacts. You drive the loop without ever running the server yourself.
Invocation forms
/functional-testing <NN-slug>— drive a single scenario./functional-testing all— drive every scenario inSTATE.mdwhose status is not yet final (i.e. notOKand notFAIL), in order.
Scenario status lifecycle
STATE.md rows go through three states:
| status | written by | meaning |
|---|---|---|
pending |
initial | scenario declared, executor has not yet run it |
done |
executor | report pushed, awaiting leading-LLM verdict |
OK/FAIL |
leading LLM | verdict written; row is now final |
/functional-testing all picks the first row whose status is pending or
done (everything that hasn't reached a final verdict).
Loop per scenario
-
Read state. Open
tests/functional/STATE.md. Confirm the scenario exists and its status. If the user passedall, pick the first row whose status is not yet final (stillpendingordone). -
Refuse if not your turn. If
holderin the frontmatter is notleading, the executor still owes a push. Tell the user, stop. -
Read the spec, NOT the expected. Open
tests/functional/scenarios/<slug>/spec.md. Do NOT openexpected.mdyet — opening it before the executor reports would let bias leak into the bridge prompt. -
Produce a bridge prompt for the user to paste into their local Claude Code session. Template:
Tu es dans le repo zendesk-mcp-server, branche locale doit être à jour avec origin/<branch-from-STATE>. Lis tests/functional/scenarios/<slug>/spec.md et applique strictement ses instructions. Ne lis PAS expected.md — c'est le critère de verdict, le voir biaiserait ton rapport. Écris tests/functional/reports/<slug>.raw.json + tests/functional/reports/<slug>.report.md. Quand fini, mets à jour tests/functional/STATE.md (status=done, holder=leading), commit et push. Préviens-moi.
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.
- 6d ago First seen · 114 lines · 83 tokens per session scan A 89460032eade
functional-testing is a skill published in the GitHub repository fruggr/zendesk-mcp-server (4 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 1,265 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-31.
Other skills, from other repositories
blazemeter-performance-testing
Comprehensive guide for BlazeMeter Performance Testing, including load configuration, reporting, JMeter configuration, Taurus, scenarios, and advanced features. Use when working with Performance tests for (1) Configuring load settings and distribution, (2) Creating and running tests (JMeter, Browser, URL/API…
blazemeter-api-reference
Comprehensive reference for BlazeMeter REST APIs, including authentication, identifiers, and API endpoints. Use when working with BlazeMeter APIs for (1) Understanding BlazeMeter REST API structure, (2) Authenticating API requests, (3) Obtaining identifiers (Workspace ID, Project ID, Test ID, etc.), (4) Using Test…
blazemeter-private-locations
Comprehensive guide for BlazeMeter Private Locations, including Radar Agent, installation (Docker, Kubernetes, Helm), configuration, management, and troubleshooting. Use when working with Private Locations for (1) Installing agents (Docker, Kubernetes, Helm Chart), (2) Configuring Radar Agent for API Monitoring, (3)…
blazemeter-administration
Comprehensive guide for BlazeMeter Administration, including workspaces, projects, security, alerts, and team management. Use when working with administration for (1) Managing workspaces and projects, (2) Configuring security settings (SAML SSO, 2FA, API keys), (3) Creating workspace alerts, (4) Managing private…
blazemeter-functional-testing
Comprehensive guide for BlazeMeter Functional Testing, including GUI Functional Tests, API Tests (deprecated), Action Library, and debugging. Use when working with Functional Testing for (1) Creating GUI Functional Tests (YAML, Java IDE, Python IDE), (2) Managing Functional Tests (duplicate, delete, move, rename), (3)…
blazemeter-getting-started
Getting started guides for BlazeMeter, including onboarding, migration guides, continuous testing journey, glossary, and mobile testing. Use when getting started with BlazeMeter for (1) Navigating BlazeMeter University onboarding, (2) Migrating from Runscope or JMeter, (3) Understanding the continuous testing journey…