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 monoes/monomind --skill verification-qualitygit clone --depth 1 https://github.com/monoes/monomindWrote 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/monoes/monomind/verification-quality)<a href="https://agentmods.dev/skills/monoes/monomind/verification-quality"><img src="https://agentmods.dev/badge/skills/monoes/monomind/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/monoes/monomind/verification-quality"><img src="https://agentmods.dev/badge/skills/monoes/monomind/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.00026 | $0.03741 |
| Opus 5.5 | $0.00010 | $0.01496 |
| Sonnet 5.5 | $0.00005 | $0.00748 |
| Haiku 4.5 | $0.00003 | $0.00374 |
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 2d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verification-quality — Evidence Before Claims
Overview
Claims without evidence are noise. "It works", "tests pass", "I fixed it" — none of these mean anything until verified against the codebase, the test suite, and the build.
This skill wires four concepts to monomind's real command surface: truth scoring
(a 0.0–1.0 confidence score from citable evidence), an evidence-before-claims
protocol (require file:line, test names, or build output before marking done),
auto-rollback (regression detection via analyze diff, revert via git), and a
multi-angle quality workflow (correctness, tests, security, performance, docs).
Core principle: NO CLAIM IS TRUE UNTIL VERIFIED AGAINST EVIDENCE.
Iron Law:
NO "DONE" WITHOUT A TRUTH SCORE ≥ 0.95 BACKED BY CITABLE EVIDENCE
If you cannot point to a file:line, a passing test name, or a green build, you
have not finished. You have started.
When to Use
Use for ANY task that ends in a claim of completion: "I implemented X", "the bug is fixed", "tests pass", "ready to ship", or any agent-returned work.
Use this ESPECIALLY when: the agent (or you) is in a hurry — that's when false claims slip in; the change touches security, money, auth, or data integrity; a previous attempt already failed; you're about to commit, push, open a PR, or merge.
Don't skip when: "it's a tiny change" (tiny changes break tests too) or "I'm sure" (confidence without evidence is the failure mode this skill prevents).
The Real Command Surface
These are the ONLY commands this skill wires to. Anything else is invented.
| Command | What it does | Phase |
|---|---|---|
monomind analyze diff |
Git diff risk + change classification | Evidence, regression |
monomind analyze code |
Static code analysis | Verification |
monomind analyze deps --security |
Dependency CVEs | Verification |
monomind analyze complexity |
Cyclomatic complexity | Verification |
monomind analyze symbols |
Extract functions/classes/types | Evidence |
monomind analyze imports |
Import graph | Verification |
monomind security scan |
Vulnerability + secret scan | Verification |
monomind security secrets |
Dedicated secret detection | Verification |
monomind security audit |
Security audit log | Verification |
monomind performance benchmark |
Run benchmarks (wasm/memory/search) | Evidence |
monomind performance metrics |
View/export metrics | Monitoring |
monomind performance bottleneck |
Identify bottlenecks | Verification |
monomind doctor / doctor --fix |
28 health-check categories | Baseline, monitoring |
monomind hooks metrics |
Learning-hook metrics | Monitoring |
monomind hooks intelligence |
Neural/MoE/HNSW status | Monitoring |
monomind monograph search |
Knowledge graph search (BM25/semantic/hybrid) | Evidence |
monomind monograph build |
Build/rebuild the knowledge graph | Baseline |
monomind tokens dashboard |
Token spend | Monitoring |
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.
- 2d ago First seen · 350 lines · 26 tokens per session scan A cbe99a43c740
verification-quality is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 26 tokens to every session and 3,741 once invoked, about $0.0001 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-10-26.
Other skills, from other repositories
developing-openrig
Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file owns a behaviour, choosing which tests to run, testing a change without disturbing the OpenRig daemon your own session runs on, judging whether a diff touches a high-risk area, or preparing a pull request. Not…
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.
validate-harness
Release-readiness umbrella check for a scaffolded harness — runs doctor, witness verify, hardcoded-path scan, MCP server config, and GCP Secret Manager validation in one shot. Exits non-zero if any sub-check fails.
oma-debug
Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
claim-check
Claim checker that audits a coding agent's statements that tests pass or a build is clean against its own session transcripts: whether a matching run happened before the claim, whether it passed, and whether code changed after it. Use when the user asks whether the agent really ran the tests, how often it said tests…