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/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/fruggr/zendesk-mcp-server/functional-testing"><img src="https://agentmods.dev/badge/skills/fruggr/zendesk-mcp-server/functional-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.00083 | $0.01265 |
| Opus 5.5 | $0.00033 | $0.00506 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (14 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 1,265 once invoked, about $0.0003 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-31.
Other skills, from other repositories
opik-test
Turn a failing Opik trace (or a described failure) into a repeatable regression check — a test-suite item with the trace's input and one or two binary assertions — so a fix can be verified by the compare skill. Works over the SDK; uses the MCP write tool when connected. Returns the suite, the item, and the assertion.…
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…
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…
quantum-circuit-verification
A local checker for deciding whether two small OpenQASM 2 quantum circuits perform the same quantum transformation. OpenQASM 2 is a text format for describing quantum circuits.
qec-memory-experiment
A local simulation workflow for testing error correction in a small surface-code quantum memory. It adds a defined error rate, samples measurement results, and uses a matching decoder to estimate logical errors.
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…