Borrowing it
Nothing to install: this file belongs to Cyruskraad/codex-claude-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/Cyruskraad/codex-claude-mcp/main/.agents/skills/verifying-mcp-delivery/SKILL.mdgit clone --depth 1 https://github.com/Cyruskraad/codex-claude-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/cyruskraad/codex-claude-mcp/verifying-mcp-delivery)<a href="https://agentmods.dev/skills/cyruskraad/codex-claude-mcp/verifying-mcp-delivery"><img src="https://agentmods.dev/badge/skills/cyruskraad/codex-claude-mcp/verifying-mcp-delivery/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/cyruskraad/codex-claude-mcp/verifying-mcp-delivery"><img src="https://agentmods.dev/badge/skills/cyruskraad/codex-claude-mcp/verifying-mcp-delivery.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.00037 | $0.00367 |
| Opus 5 | $0.00018 | $0.00183 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
verifying-mcp-delivery 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.
What it actually says
verifying-mcp-delivery
Report the highest evidence level actually rerun without upgrading weaker proof.
Use when
- Verify this MCP delivery before handoff.
- Prove which delivery layers currently pass.
Do not use when
- Do not use as a substitute for fixing a known failure.
- Do not infer hosted health from local success.
Required inputs
- Requested evidence level.
- Current target.
- Existing evidence and its freshness.
Workflow
Read and follow the canonical playbook references/verify-and-recover.md at ../noodle-seed/references/verify-and-recover.md. It owns the workflow; do not recreate it here or load the command catalog speculatively.
Load references/test-in-hosts.md at ../noodle-seed/references/test-in-hosts.md only when the playbook or observed evidence names that concern.
Verification evidence
Every dependency below the requested level passes now, or the first unproven layer is explicit.
Recovery paths
Hand a concrete failing layer to debugging-mcp-delivery with all passing evidence preserved.
Stop conditions
Stop after the requested level passes or the first bounded failure is isolated.
Handoff contract
Pass the selected outcome, explicit target, changed files, commands run, passing evidence, first unproven evidence layer, sanitized failure, remaining authority, and exact next action. The receiving skill continues from that layer; do not restart discovery or discard prior proof.
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 · 48 lines · 37 tokens per session scan A 89512d030215
verifying-mcp-delivery is a skill published in the GitHub repository Cyruskraad/codex-claude-mcp (0 stars, last pushed 14d ago), licensed MIT. It adds 37 tokens to every session and 367 once invoked, about $0.0002 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.