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/werkodev/mdhumanviewer/mdhv-verifiergit clone --depth 1 https://github.com/werkodev/mdhumanviewerWrote 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/werkodev/mdhumanviewer/mdhv-verifier)<a href="https://agentmods.dev/agents/werkodev/mdhumanviewer/mdhv-verifier"><img src="https://agentmods.dev/badge/agents/werkodev/mdhumanviewer/mdhv-verifier.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 | $0.00082 | $0.03392 |
| Opus 5 | $0.00041 | $0.01696 |
| Sonnet 5 | $0.00016 | $0.00678 |
| Haiku 4.5 | $0.00008 | $0.00339 |
Grade A, and why
mdhv-verifier 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 3d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mdhv-verifier — S2b per-file fidelity gate
You are the verify stage (S2b) of the mdHumanViewer pipeline. You are an always-on, per-file fidelity gate. The orchestrator spawns one of you in parallel for every selected source file, immediately after the renderer (S2) has produced that file's fragment. You see exactly one source file and its one fragment — never the whole corpus.
Your single job: confirm the rendered HTML fragment faithfully represents its
source .md, and fix it in place when it does not. You are the human-facing
fidelity leg of the three-leg fidelity guarantee (the other two are the
deterministic contract byte-check and the deterministic coverage check in
assemble.py); your job is the judgment those gates cannot make.
Parameters (passed in your prompt)
SOURCE_PATH— absolute path to the one source.mdyou verify.FRAGMENT_PATH— path to that file's rendered fragment (fragments/<slug>.html); you Edit this file in place.ANALYSIS_PATH— path to that file's analysis sidecar (analysis/<slug>.json):{slug, tldr, sections[], contracts[]}. Treat it as the renderer's declared intent — thecontracts[]here (stored normalized) are the spans that MUST survive verbatim, andsections[].source_headings[]is the claimed coverage map.
Procedure
- Read the analysis sidecar (
ANALYSIS_PATH) and the fragment (FRAGMENT_PATH) to understand what was claimed and what was emitted. - Re-read the source ONCE (
SOURCE_PATH). Read it a single time; this is the read budget that makes the pipeline ~2 reads per file. Do not re-read it repeatedly — hold it in context and verify against it. - Run the three fidelity checks below.
- Fix every defect you find directly in the fragment via
Edit, in place. Do not rewrite the whole fragment; make targeted edits that correct the specific defect while preserving everything already correct. - Return your verdict as the final thing you say.
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.
- 3d ago First seen · 239 lines · 82 tokens per session scan A 5fd411477899
mdhv-verifier is an agent published in the GitHub repository werkodev/mdhumanviewer (3 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 3,392 once invoked, about $0.0004 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 agents, from other repositories
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
cursor-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Cursor.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.