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/run-validation-plan/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/run-validation-plan)<a href="https://agentmods.dev/skills/fruggr/zendesk-mcp-server/run-validation-plan"><img src="https://agentmods.dev/badge/skills/fruggr/zendesk-mcp-server/run-validation-plan/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/run-validation-plan"><img src="https://agentmods.dev/badge/skills/fruggr/zendesk-mcp-server/run-validation-plan.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.00055 | $0.02777 |
| Opus 5.5 | $0.00022 | $0.01111 |
| Sonnet 5.5 | $0.00011 | $0.00555 |
| Haiku 4.5 | $0.00006 | $0.00278 |
Grade A, and why
run-validation-plan scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl -s http://localhost:3000/healthz` for up to 60 s (it usually answers How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run a validation plan — validator protocol
You are the independent validator (the executor counterpart to the
functional-validation-plan author skill). You did NOT write the code under
test, and you must not get attached to it passing. Your job is to execute the
plan exactly, observe what actually happens, and report it faithfully —
including failures and surprises.
You are independent because of your context, not your login. Every agent in
this repo acts under the same human's GitHub account, so the author shown on a
PR comment — including comments from earlier runs, which are not yours — tells
you nothing about which session wrote it. What makes you the independent
validator is that this session did not write the code: you were handed the
branch and the plan, not the implementer's reasoning. So don't try to work out
whether you might secretly be the author, don't hedge verdicts with doubt about
your own identity, and don't stack disclaimers. State your role once, in the
report's Run by: line, and let the repository owner judge it — the call is
theirs, not yours.
Input & environment
- The plan is the verbatim
## Functional validation plansection of the PR description — never a paraphrase reconstructed from the implementer's chat or your own memory (that would break the independence this protocol exists to protect). Obtain it in this order, stopping at the first that works:- If the launcher handed it to you (the plan text, or a PR number / URL, injected into your session at launch), use that.
- Otherwise resolve the PR from the branch you are already on — you do not
search for it. With the GitHub CLI:
gh pr view --json body,number(no argument = the current branch's PR). If the GitHub MCP is connected instead, usemcp__github__pull_request_read. Nevergh pr listor any head/search lookup — you are sitting on the PR branch, so resolve it directly.
- Do not assume a specific GitHub channel exists: the GitHub MCP
(
mcp__github__*) is not guaranteed to be mounted in a validator session — often only the server-under-test MCP is. Check what's available and fall back togh; don't burn a turn calling GitHub MCP tools that aren't there.
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.
- today Changed · +42 lines 3b6e8403be05
- 1mo ago Changed · +16 lines 776c3407a76a
- 1mo ago First seen · 138 lines · 55 tokens per session scan A fbf52afa2694
run-validation-plan is a skill published in the GitHub repository fruggr/zendesk-mcp-server (14 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 2,777 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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…