Borrowing it
Nothing to install: this file belongs to sponge-b0b/Polaris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sponge-b0b/Polaris/main/.agents/skills/deduplicate-code/SKILL.mdgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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/skills/sponge-b0b/polaris/deduplicate-code)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/deduplicate-code"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/deduplicate-code/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/skills/sponge-b0b/polaris/deduplicate-code"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/deduplicate-code.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.00032 | $0.01546 |
| Opus 5.5 | $0.00013 | $0.00618 |
| Sonnet 5.5 | $0.00006 | $0.00309 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
deduplicate-code 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Duplication Checks
Authoritative procedure composition
Before executing this skill, read .agents/skills/deduplicate-code/PROCEDURE.md in full.
That file preserves the complete established duplicate-code procedure. This SKILL.md is
the authoritative entrypoint and owns the differential-causality and control-plane
corrections below; on conflict, this file wins.
All retained whole-repository scanner scope, finding classification, consolidation, suppression-merit, migration/test-surface, forbidden-silencing, rerun, and evidence rules remain normative except where this entrypoint explicitly replaces historical-baseline causality.
Ticket-differential uses the Execution Anchor
When delegated by $implement-ticket, ticket-differential receives:
TICKET_BASELINE
immutable historical ticket lineage only
EXECUTION_ANCHOR
exact fetched shared-branch commit admitted before this implementation attempt
candidate
exact working candidate relative to EXECUTION_ANCHOR
For ticket-differential, EXECUTION_ANCHOR is the comparison base.
TICKET_BASELINE is not the scanner/differential baseline and must never be used to create
the isolated comparison worktree for the current attempt.
Run whole-repository candidate scans in the current exact worktree as before. Establish
comparison evidence against an isolated read-only EXECUTION_ANCHOR worktree/ref.
A reusable ticket-differential comparison scan is valid only while all of these are unchanged:
- exact
EXECUTION_ANCHOR; - scanner executable/toolchain versions;
- Execution-Anchor Arid/JSCPD configuration and suppression-policy files;
- scan scope/configuration semantics used for the differential comparison.
Interpret the retained four causality states against EXECUTION_ANCHOR:
candidate-introduced
candidate-expanded
baseline-identical
unresolved
Here baseline-identical means identical to the Execution Anchor. Legitimate
shared-branch/prerequisite/workflow changes between historical Ticket baseline and Execution
Anchor are inherited upstream state and cannot become ticket-attributable duplicate debt.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +75 lines · +1 tokens per session 6d824663cc89
- 6d ago Changed · -350 lines · -1 tokens per session c5c3a8cee452
- 24d ago Changed · +42 lines 58f5a6d71f92
- 25d ago Changed · +12 lines 096ff6038393
- 1mo ago Changed · +64 lines · -2 tokens per session 889a42a2d32f
- 1mo ago Changed · +82 lines d4aa8084880e
- 1mo ago Changed · +218 lines · -4 tokens per session 6976cc6eba4a
- 1mo ago First seen · 50 lines · 38 tokens per session scan A 58bccdeebbb1
deduplicate-code is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 1,546 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.