Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/evoclaw/amplify/results-verification-protocolnpx skills add EvoClaw/amplify --skill results-verification-protocolgit clone --depth 1 https://github.com/EvoClaw/amplifyWrote 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/evoclaw/amplify/results-verification-protocol)<a href="https://agentmods.dev/skills/evoclaw/amplify/results-verification-protocol"><img src="https://agentmods.dev/badge/skills/evoclaw/amplify/results-verification-protocol.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.00036 | $0.00711 |
| Opus 5 | $0.00018 | $0.00356 |
| Sonnet 5 | $0.00007 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
results-verification-protocol 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Results Verification Protocol (Discipline Layer)
Overview
Claiming a result without verification is fabrication, not efficiency. This skill is ALWAYS active.
Core principle: Evidence before claims, always.
Violating the letter of this rule is violating the spirit of this rule.
The Iron Law
NO RESULT CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the verification command in this message, you cannot claim the result.
The Gate Function
BEFORE claiming ANY result status:
1. IDENTIFY: What command or check proves this claim?
2. RUN: Execute it now, fresh, complete
3. READ: Full output — every line, every number
4. VERIFY: Does the output actually support the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence attached
5. ONLY THEN: Make the claim
Skip any step = fabrication, not verification
Research-Specific Verification Requirements
| Claim | Requires | Not Sufficient |
|---|---|---|
| "Tests pass" | Test output showing 0 failures | "Should pass", previous run |
| "Method outperforms baseline" | Numbers from BOTH methods, statistical test result (p-value/CI) | One method's numbers, "looks better" |
| "Analysis complete" | All analysis outputs present and inspected | Script ran without errors |
| "Experiment finished" | Full results table, all seeds, all conditions | Partial results, single seed |
| "Paper ready" | Checklist of every claim mapped to supporting evidence | "All sections written" |
| "Results are significant" | Statistical test output with exact values | Eyeballing differences |
| "Reproducible" | Independent re-run producing same results | "Same code, should work" |
Forbidden Phrases
Never use these without attached evidence:
- "should work"
- "looks correct"
- "probably fine"
- "seems good"
- "appears to outperform"
- "likely significant"
Replace with evidence. Every time.
Red Flags — STOP
- Expressing satisfaction before running verification
- Citing numbers from memory instead of fresh output
- Reporting partial results as complete
- Claiming significance without a statistical test
- Trusting a previous run instead of re-running
- Summarizing results you haven't fully read
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 · 95 lines · 36 tokens per session scan A 98a9e5e39e85
results-verification-protocol is a skill published in the GitHub repository EvoClaw/amplify (12 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 711 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-30.
Other skills, from other repositories
dingtalk_channel_connect
Use a headed browser to automatically complete DingTalk channel integration for QwenPaw. Applicable when the user mentions DingTalk, developer console, Client ID, Client Secret, bot, Stream mode, binding or configuring a channel. Supports pausing when a login page is detected and resuming after the user logs in.
当用户需要对PDF文件进行任何操作时，请使用此技能。包括从 PDF 中读取或提取文本/表格、合并多个 PDF、拆分 PDF、旋转页面、添加水印、创建新PDF、填写PDF表单、加密/解密 PDF、提取图片，以及对扫描版 PDF 进行 OCR 使其可搜索。如果用户提到 .pdf 文件或要求生成 PDF，请使用此技能。.
make_plan
For external plan request scenarios, guides the Agent to request a clear, actionable, step-by-step plan from a stronger Agent via listagents and chatwithagent, emphasizing that the plan is executed by the requester, not by the consulted Agent.
new
Create a new project to start development quickly.
oss-upload
Upload local files to Tencent COS (oss.1024code.com CDN) using coscli. Use when user wants to upload a file to CDN/OSS, or deploy static assets.
officecli-word-form
Use this skill to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document'…