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 skills add mattmre/EVOKORE-MCP-PUBLIC --skill verification-qualitygit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote 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/mattmre/evokore-mcp-public/verification-quality)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/verification-quality"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/verification-quality/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/mattmre/evokore-mcp-public/verification-quality"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/verification-quality.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.00036 | $0.00504 |
| Opus 5 | $0.00018 | $0.00252 |
| Sonnet 5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
verification-quality 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 11d 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
Verification Quality Skill
Applies tiered truth scoring to verify work meets environment-specific quality thresholds. Produces machine-readable JSON output for CI gate integration.
Trigger
Use this skill when:
- Completing a feature implementation and need to verify correctness
- Validating test coverage meets environment thresholds
- Generating CI gate output for automated quality enforcement
Truth Score Formula
truth_score = (tests_passing_pct * 0.4) + (type_check_passes * 0.3) + (lint_clean * 0.2) + (no_regressions * 0.1)
Environment Thresholds
| Environment | Minimum Truth Score |
|---|---|
| Production | 0.99 |
| Staging | 0.95 |
| Development | 0.80 |
| CI Gate | 0.90 |
Output Format
{
"truth_score": 0.97,
"threshold": 0.95,
"gate_passed": true,
"breakdown": {
"tests_passing_pct": 1.0,
"type_check_passes": true,
"lint_clean": true,
"regressions_detected": 0
},
"environment": "staging",
"timestamp": "2026-04-15T00:00:00Z"
}
Usage
Run this skill after completing any feature or fix:
- Establish environment context (prod/staging/dev)
- Run test suite and capture pass rate
- Run TypeScript compiler and linter
- Compute truth_score
- Compare against threshold
- Emit JSON gate output
Integration
- Works with AGT-017 (Quality Engineer) for defect prediction
- Feeds into AGT-021 (Release Engineer) release gates
- Output is consumed by CI pipelines via exit code (0=pass, 1=fail)
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.
- 11d ago First seen · 70 lines · 36 tokens per session scan A eb16a68bba31
verification-quality is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 504 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
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
verify-before-done
Proves work with tests, diffs, and logs before sign-off.
verification-quality
Truth scoring, code-quality verification, and automatic rollback with a high accuracy threshold. Use when validating agent output before it ships, gating changes on quality, or adding a verify-and-rollback safety loop.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
Verification Before Completion
Mandatory empirical verification suite execution before declaring task completion.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.