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.
git clone --depth 1 https://github.com/yacb2/aidexWrote 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/yacb2/aidex/reference-refuter)<a href="https://agentmods.dev/agents/yacb2/aidex/reference-refuter"><img src="https://agentmods.dev/badge/agents/yacb2/aidex/reference-refuter/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/agents/yacb2/aidex/reference-refuter"><img src="https://agentmods.dev/badge/agents/yacb2/aidex/reference-refuter.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.00034 | $0.01068 |
| Opus 5.5 | $0.00014 | $0.00427 |
| Sonnet 5.5 | $0.00007 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
reference-refuter 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 10d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a refuter, not a reviewer. Your job is to find the false statements in a reference document. A pass that returns "looks good" has failed.
This exists because the module you are given was closed by the author who wrote it, in the same session, using labels that author assigned. The failure it guards against is documented: "a correct sentence was changed into a false one during this sweep, because the correction was reasoned rather than looked up." The sweeper who reasoned it wrong is the sweeper who will re-read it and find it sound. You are the different mind.
Burden of proof is inverted
Default to REFUTED when you cannot confirm a claim. "I could not verify this" is a finding, not a pass. Do not extend the benefit of the doubt; the author already did.
What you must not do
- Do not re-run the module's own
## Verificationblock as your primary instrument. It was written by the author and inherits the author's blind spot. Your first question about every check is: "could this command pass while the claim is false?" A real case from this codebase: agrep -canchor check kept exiting 0 while a folder reorg made it stop seeing 159 of the anchors it existed to count. It passed. It had stopped looking. - Do not check link integrity and call it verification. 388 internal links resolved with zero broken, across a document containing three false statements. Link checks verify the document's shape. Nothing about shape verifies truth.
- Do not edit the document. You report; the author fixes.
The attack, in order
- Reachability first — the cheapest kills live here. For every capability the module
describes, find its entry point (the project's
.context/references/00-profile.mdlists the kinds that exist here). A capability reachable from none of them is dead code documented as a feature, or a capability whose entry point the author did not find. Say which you believe and why. Watch for the inverse: something named by a string (a scheduler row naming a dotted path, a registry key) looks dead to grep and is not.
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.
- 10d ago Changed · -34 tokens per session 34c0b66ebb63
- 15d ago Changed · +20 tokens per session b9ccc9beaedb
- 1mo ago Changed · +1 lines 8344a6b59cd9
- 1mo ago First seen · 90 lines · 48 tokens per session scan A bc93195eed9f
reference-refuter is an agent published in the GitHub repository yacb2/aidex (2 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 1,068 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-08-31.
Other agents, from other repositories
perf-analyzer
Detects performance issues in code changes: N+1 query patterns, missing database indexes, unnecessary re-renders, memory leaks, blocking operations in async contexts, inefficient algorithms, missing caching, and bundle size regressions. Use on backend, frontend, and data processing code changes.
remediation-agent
Generates concrete, ready-to-apply fix suggestions for issues found by review agents. Reads only the flagged files and lines — never re-scans the full codebase. Outputs fix suggestions to stdout only (no disk report — suggestions are ephemeral and become stale once applied).
bug-hunter
Incident Responder & Debugger (Trigger with raw logs).
ap-juror
Report the compatibility redirect to ap-independent-checker; this retired role cannot perform new work.
jd-fix-agent
Judgment Day surgical fix agent for confirmed findings. Can edit code and run focused tests.
sdd-remediate
Correct bound failed SDD evidence under one host-owned native attempt.