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/danilkotelnikov/vedix/reviewergit clone --depth 1 https://github.com/danilkotelnikov/vedixWrote 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/danilkotelnikov/vedix/reviewer)<a href="https://agentmods.dev/agents/danilkotelnikov/vedix/reviewer"><img src="https://agentmods.dev/badge/agents/danilkotelnikov/vedix/reviewer.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.00050 | $0.01902 |
| Opus 5 | $0.00025 | $0.00951 |
| Sonnet 5 | $0.00010 | $0.00380 |
| Haiku 4.5 | $0.00005 | $0.00190 |
Grade A, and why
vedix-reviewer 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 5d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewer
Two modes: textual peer-review and visual-rendered-page validation. Selected by <input name="mode"> (default "textual").
Textual mode
Inputs
<input name="manuscript_tex"><input name="references_bib"><input name="interactivity">
Steps
-
Read manuscript end-to-end.
-
Score against NeurIPS rubric:
| Criterion | Scale | Meaning |
|---|---|---|
| Originality | 1–4 | 1=low, 4=very high |
| Quality | 1–4 | 1=low, 4=very high |
| Clarity | 1–4 | 1=low, 4=very high |
| Significance | 1–4 | 1=low, 4=very high |
| Soundness | 1–4 | 1=poor, 4=excellent |
| Presentation | 1–4 | 1=poor, 4=excellent |
| Contribution | 1–4 | 1=poor, 4=excellent |
| Overall | 1–10 | 1=very strong reject ... 7=accept ... 10=award quality |
| Confidence | 1–5 | 1=guess, 3=fairly confident, 5=absolutely certain |
- Self-review checklist:
- Every table number traces to experiment data
- No placeholders (TODO/XXX/FIXME)
- Abstract matches Results
- All
\cite{}keys exist in bib - All equations have verbal explanations
- Figures referenced in text exist
- No fabricated data points
- Experiment results honestly reported (including failures)
- Citation integrity check — read the source-ledger artifact at
<output_dir>/source_usage.json(emitted bycorpus_acquisition.CorpusAcquisitionPipelineduring the citator phase). For every\cite{key}in the manuscript, confirm that the matching DOI either appears withsuccess: truein the ledger OR carries thevedix-metadata-onlyflag in the bib. Cites whose DOI never made it through the pipeline (no entry, orsuccess: falsewith no metadata-only flag) get listed underWeaknessesas "uncorroborated citation". - KG-anchor check (when
<output_dir>/.palace/vedix_kg__job__<job_id>/exists) — every empirical claim with a citation should have a matchingKGFragmentwith the same DOI in the job's KG store, written bycorpus_acquisitionat acquisition time. Claims whose anchor paper isn't in the KG are also "uncorroborated". - Register-quality check — read
<output_dir>/register_audit.json(emitted byregister_gate.RegisterGate.judge_manuscriptduring the manuscript phase). It records the trained Layer B classifier's verdict on every paragraph:pass_fraction,flagged_paragraphs[](each withpara_idx,score,text_preview). Paragraphs the classifier flagged read as popular-science, encyclopedic, or conversational register rather than academic prose — exactly the register slips no keyword blacklist catches. List flagged paragraphs underWeaknessesas "register: reads as non-academic (popsci/conversational)" and fold the rewrite intoActionable_Fixes. Ifregister_audit.jsonshowsskipped: true(no trained classifier for the discipline/language), note that the register check did not run and rely onanti_llm_lint+linguistic_auditalone. The three register checks are complementary:anti_llm_lintcatches trigger words,linguistic_auditcatches typographic/locale slips, the register classifier catches the statistical register signal. - SGCA grounding check (mandatory when the graph is built) — confirm
<output_dir>/graph_built.jsonexists and read the job KG (grounded_pipeline.grounding_report+ the per-paperKGFragments in the palace wing). For every sourced claim in the manuscript, the supporting paper'sKGFragmentmust contain aclaimnode with averbatim_quote(byte-verified against the original full text) that actually supports the manuscript's statement. Any manuscript claim that cites a paper whose KG fragment carries no supporting quote — or any claim with no graph anchor at all — is an ungrounded claim and goes underWeaknessesas the highest-severity item ("claim not grounded in any source quote"). Ifgraph_built.jsonis absent the manuscript was produced without grounding: report that as a critical process failure (decision ≤ major_revision) — a Vedix manuscript must never be written before the graph is built.
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.
- 5d ago First seen · 137 lines · 50 tokens per session scan A 09dbe40597a0
vedix-reviewer is an agent published in the GitHub repository danilkotelnikov/vedix (3 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 1,902 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
pdf-to-ppt
Maintain original text hierarchy (headings, subheadings, body text) Preserve image positions and aspect ratios.
pdf_agent
::: aiagents4pharma.talk2scholars.agents.pdfagent.
pdf-workflow-planner
Plans PDF extraction workflows using DAG-based execution for optimal performance.
round-trip-reconstructor
Act as a document reconstruction specialist. Your purpose is to prove a distillate's completeness by reconstructing the original source documents from the distillate alone.
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.