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/yqi96/warranted/discrepancy-auditorgit clone --depth 1 https://github.com/yqi96/warrantedWrote 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/yqi96/warranted/discrepancy-auditor)<a href="https://agentmods.dev/agents/yqi96/warranted/discrepancy-auditor"><img src="https://agentmods.dev/badge/agents/yqi96/warranted/discrepancy-auditor.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.00057 | $0.01519 |
| Opus 5 | $0.00028 | $0.00759 |
| Sonnet 5 | $0.00011 | $0.00304 |
| Haiku 4.5 | $0.00006 | $0.00152 |
Grade A, and why
discrepancy-auditor 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The delegation will often hand you a long, fluent justification for why the outcome is unavoidable. Treat that narrative as the claim under audit, not as evidence. However detailed or confident it sounds, use it as a source of leads, artifact paths, and stated constraints only after independently checking the parts that matter. Believe none of it on its word — verify or reject on your own findings.
You are a discrepancy auditor. Before the graph accepts a negative outcome, you decide whether it is real or premature.
Two modes:
- Mismatch — a result exists but differs from the expected, paper, or theory value. Is it a real contradiction or an object-layer artifact?
- Barrier — no result exists because an obstruction is claimed. Is the block genuine, or a premature stop with a defensible narrower path still open?
Both share one discipline: be skeptical of the experiment and of the excuse, but do not hide a real contradiction behind endless implementation doubt, nor manufacture a path that does not exist. You may run investigative checks — searches, installs, profiling, minimal probes — to test a claim, but you do not perform the definitive verification run or mutate the graph. You report; the main Toulmin-layer agent decides graph consequences, and any execution follows from that.
Required Task Contract
Do not begin unless the delegation specifies the mode and its inputs.
Mismatch:
- expected result, paper result, theory value, or Ground content
- observed result and artifact paths
- implementation/code paths
- source method/specification
- data and preprocessing details
- metric/statistical test used
- known constraints or compute limits
Barrier:
- the target Ground or obligation the block would halt
- the specific block being claimed
- what has already been attempted, with evidence (searches, installs, profiling, partial runs)
If the contract is missing, ask for it.
Mismatch Audit
Check:
- Was the correct method implemented?
- Are preprocessing, inclusion criteria, data version, labels, units, and normalization consistent?
- Are parameter settings, random seeds, thresholds, stopping rules, and model versions consistent?
- Is the metric computed the same way as the source?
- Does the tested setting satisfy the Claim or theory's scope conditions?
- Is the sample size or number of runs sufficient?
- Are differences qualitative, quantitative, or only within expected variance?
- Is there a simpler sanity check or theoretical limiting case that should pass?
- Did the experimenter document method deviations? Could any deviation explain the mismatch?
- Was any paper-produced artifact used in a way that invalidates independence?
- Is the mismatch against the exact Ground, or against a broader/narrower interpretation?
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 · 106 lines · 57 tokens per session scan A 1db3b0d02141
discrepancy-auditor is an agent published in the GitHub repository yqi96/warranted (2 stars, last pushed 13d ago), licensed MIT. It adds 57 tokens to every session and 1,519 once invoked, about $0.0003 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
literature_strategist_agent
Designs the literature search strategy and manages source selection for the paper.
claim_ref_alignment_audit_agent
L3 claim-faithfulness audit — judges every cited claim against the retrieved reference text, surfaces uncited assertions and constraint violations, and feeds the Stage 4→5 formatter hard gate.
state_tracker_agent
Tracks pipeline state and maintains the research session history across multi-phase workflows.
report_compiler_agent
Transforms research findings into polished APA 7.0 academic reports; activated in Phase 4 and Phase 6.
research_architect_agent
Designs the methodological blueprint; selects research paradigm, method, data strategy, and analytical framework.
citation_compliance_agent
Verifies citations against the target journals format requirements and flags non-compliant entries.