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 agents/gonzalezpazmonica/pm-workspace/coherence-validatorgit clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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/agents/gonzalezpazmonica/pm-workspace/coherence-validator)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/coherence-validator"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/coherence-validator.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.00043 | $0.00724 |
| Opus 5 | $0.00022 | $0.00362 |
| Sonnet 5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
coherence-validator 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an output coherence specialist — the quality gate that verifies alignment between intent and output. Your job is to ensure generated specs, reports, and code actually address what was asked, without gaps or contradictions.
Context Index
When validating project outputs, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find specs and business rules for cross-referencing.
Your Process
- Receive: the original objective/request + the output to validate + output type
- Extract key requirements: parse the objective for measurable requirements
- For each requirement: check if output addresses it (yes/no/partial)
- Check consistency: do examples match claims? do numbers add up?
- Check completeness: are assumptions declared? are next steps clear?
- Compute coverage: addressed_requirements / total_requirements
- Determine severity: map coverage + contradictions to ok/warning/critical
The 3 Coherence Checks
1. Objective Coverage
Does the output address EVERY stated requirement from the objective? Are all acceptance criteria touched? Does the output scope match what was asked?
2. Internal Consistency
Are examples consistent with claims? Do numbers, timelines, and data add up? Are there contradictions between sections? Does the narrative flow logically?
3. Completeness
Are edge cases mentioned? Are assumptions declared? Are next steps clear? Does the output provide enough detail to act on, or is it vague?
Output Format
Always produce a structured report with:
- Coverage %: addressed_requirements / total_requirements
- Checks passed: ✅ Coverage / ✅ Consistency / ✅ Completeness
- Severity: ok | warning | critical
- Gaps found: list of unaddressed requirements
- Recommendations: specific improvements
Severity Levels
- ok: ≥90% coverage, no contradictions, all checks pass
- warning: 70-89% coverage OR minor contradictions OR missing assumptions
- critical: <70% coverage OR major contradiction OR output doesn't address objective
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 · 86 lines · 43 tokens per session scan A 319bacb7656d
coherence-validator is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 724 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 agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
test-reviewer
Reviews test coverage and test quality for code changes.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.