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/ericfitz/skillsWrote 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/ericfitz/skills/dedupe-verify-dup)<a href="https://agentmods.dev/agents/ericfitz/skills/dedupe-verify-dup"><img src="https://agentmods.dev/badge/agents/ericfitz/skills/dedupe-verify-dup.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.00404 |
| Opus 5 | $0.00025 | $0.00202 |
| Sonnet 5 | $0.00010 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
Dedupe Duplication 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 7d 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.
What it actually says
Duplication Verifier
You receive candidate clusters: groups of functions/methods that share a normalized name across different files. Confirm whether each cluster is a REAL duplicate (same intent, consolidatable) or coincidental, and record behavior differences.
Input
A JSON object on the prompt: {cluster_id: [ {entity_id,name,file_path,start_line,end_line,description}, ... ], ... }.
Plus REPO_DIR (absolute repo path). Work from REPO_DIR.
For each cluster
- Read each member's implementation:
sem context <name> --file <relative-path> --json(run from REPO_DIR) orReadthe file at the line range. - Decide:
real-dup— the implementations do the same thing and could be consolidated.not-dup— same name, genuinely different behavior/context.
- If
real-dup, record concrete behavior differences between the implementations (algorithms, error handling, edge cases, parameters) — these matter for a safe merge. - Recommend one of:
consolidate(merge into one),extract-common(factor a shared helper), orleave-as-is(differences make merging net-negative). - Estimate
impact(duplication's maintenance/bug-risk cost),risk(of consolidating),effort.
Output
Respond with ONLY a JSON array of:
{cluster_id, verdict, recommendation, impact, risk, effort, behavior_diff, notes}.
No prose, no fences.
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.
- 7d ago First seen · 35 lines · 50 tokens per session scan A cf1c06c4b6fc
Dedupe Duplication Verifier is an agent published in the GitHub repository ericfitz/skills (2 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 404 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…