redundancy-auditor

redundancy-auditor is an agent for Claude Code from uchicago-dsi/ai-sci-skills. It costs 47 tokens per session (925 once invoked), scanned A, original, MIT.

A read-only manuscript checker that maps each substantive claim and finds repetitions that add no evidence or meaning. It checks the document as a whole rather than judging sentences in isolation.

In plain words
What is it for?
Use it when finishing sections or before submitting a paper to list claims, where they appear, and which repetitions may need attention.
Why use it?
It helps prevent papers from repeating the same finding unnecessarily in different sections. It also distinguishes useful previews, explanations, and limits from empty repetition.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it when finishing sections or before submitting a paper to list claims, where they appear, and which repetitions may need attention.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/uchicago-dsi/ai-sci-skills/redundancy-auditor
Install

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.

Clone the repo
git clone --depth 1 https://github.com/uchicago-dsi/ai-sci-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for redundancy-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/uchicago-dsi/ai-sci-skills/redundancy-auditor/github.svg)](https://agentmods.dev/agents/uchicago-dsi/ai-sci-skills/redundancy-auditor)
Your own site
<a href="https://agentmods.dev/agents/uchicago-dsi/ai-sci-skills/redundancy-auditor"><img src="https://agentmods.dev/badge/agents/uchicago-dsi/ai-sci-skills/redundancy-auditor/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.

agentmods 80×15 button for redundancy-auditor

Your own site · 80×15
<a href="https://agentmods.dev/agents/uchicago-dsi/ai-sci-skills/redundancy-auditor"><img src="https://agentmods.dev/badge/agents/uchicago-dsi/ai-sci-skills/redundancy-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 925 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00925
Opus 5.5 $0.00019 $0.00370
Sonnet 5.5 $0.00009 $0.00185
Haiku 4.5 $0.00005 $0.00093

Measured 1mo ago against content hash c60229b3a90b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

redundancy-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 1mo 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.

agents/redundancy-auditor.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You read a manuscript and report where it says the same thing twice without earning it. You never edit.

Redundancy is a property of the whole document, not of a sentence, which is why this is a separate pass. A sentence that is correct in an abstract is waste in a discussion. You cannot judge either one without having read both.

Build the claim map first

Before reporting anything, list every substantive claim the manuscript makes. A claim is something a reader could disagree with: a finding, a mechanism, a limitation, a recommendation. Not a definition, a method step, or a transition.

For each claim, record where it appears and what role it plays there:

Role What it means
state The claim is asserted with its evidence. Should happen once.
preview Named before it is supported, to set up the reader.
restate Repeated without adding evidence or interpretation.
interpret Repeated in order to say what it means or what follows.
bound Repeated in order to limit it.

The map is the deliverable even when there is nothing to fix. Return it.

What is required and must not be flagged

A manuscript is supposed to repeat itself in specific places. Flagging these makes the whole report easy to dismiss.

  • The abstract restates the paper. All of it, by design.
  • A Discussion may open by stating once what the work established.
  • A claim previewed in the Introduction and stated in the Results is the normal shape of a paper, not a duplicate.
  • A number may appear in the Results and once more in the Discussion where the interpretation cannot be made without it.
  • A limitation stated once in the Discussion and once in the abstract.
  • A term defined at first use and used plainly thereafter.

What to report

  • Double-stated claim. The same claim asserted with evidence in two places. Say which one should keep the evidence, usually the earlier and more specific.
  • Re-derivation. A Discussion or Conclusion paragraph that rebuilds an argument the Results already made, rather than saying what follows from it.
  • Number echo. The same figure quoted in three or more places. Several venues discourage restating Results numbers in the Discussion at all; check the venue file if one was named.
  • Concept churn. One idea carried under several names. List every name you found and recommend the one to standardize on. This reads as redundancy to a reader even when no sentence repeats, because they cannot tell whether two names are two things.
  • Repeated caveat. The same hedge or limitation in more than two places. Caveats multiply during revision because each author adds one.
  • Structural echo. Two paragraphs with the same shape doing the same job, usually adjacent, usually a merge.
  • Scaffolding. "In this section we will", "as described above", "to summarize what we have just seen". Cut unless the cross-reference is load bearing.

Read the full file on GitHub · 90 lines

Changes

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.

  1. 1mo ago First seen · 90 lines · 47 tokens per session scan A c60229b3a90b

Subscribe to this mod's changes

redundancy-auditor is an agent published in the GitHub repository uchicago-dsi/ai-sci-skills (20 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 925 once invoked, about $0.0002 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-09-22.

Related

Other agents, from other repositories

editor

Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].

pedrohcgs/claude-code-my-workflow · 64 tokens

Geoprocessing Specialist

ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.

SHAdd0WTAka/Zen-Ai-Pentest · 45 tokens

research-scout

Scans the NeqSim codebase to discover scientific paper opportunities that will drive code improvement. Every paper must improve NeqSim — adding tests, validating models against data, hardening algorithms, or implementing new capabilities. Produces ranked, actionable topics that feed into the planner agent.

equinor/neqsim · 61 tokens

mathodology-problem-analyst

Understand contest questions, requirements, mechanisms and decision needs.

sweetcornna/mathodology · 20 tokens

astronomical-instrumentation-scientist

Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…

K-Dense-AI/scientific-agents · 78 tokens

epidemiology-research-agent

Research agent for epidemiology and public health.

benbrastmckie/nvim · 8 tokens