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 skills/warpdotdev/oz-for-oss/dedupe-issuenpx skills add warpdotdev/oz-for-oss --skill dedupe-issuegit clone --depth 1 https://github.com/warpdotdev/oz-for-ossWrote 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/warpdotdev/oz-for-oss/dedupe-issue)<a href="https://agentmods.dev/skills/warpdotdev/oz-for-oss/dedupe-issue"><img src="https://agentmods.dev/badge/skills/warpdotdev/oz-for-oss/dedupe-issue.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 | $0.00046 | $0.00839 |
| Opus 5 | $0.00023 | $0.00419 |
| Sonnet 5 | $0.00009 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
dedupe-issue 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 4d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detect duplicate issues
Compare a newly filed GitHub issue against existing issues in the repository and identify likely duplicates by similarity of title and description.
Inputs
Expect the prompt to include:
- the incoming issue's number, title, and description
- the repository owner/name, so you can search issues yourself via the GitHub API or
gh api --paginate
Process
- Enumerate comparison candidates yourself. Fetch all open issues in the repository with pagination, excluding pull requests and the incoming issue itself. Use the GitHub API directly or
gh api --paginate; do not rely on a preselected candidate list from the triage prompt and do not cap the search to the newest issues. - Fetch closed issues only when they were closed within the last 7 days or when repository-specific guidance names a known canonical duplicate. Older closed issues should generally not be treated as duplicates because they may already be resolved.
- Normalize the incoming issue's title and description by lowercasing, stripping leading/trailing whitespace, and collapsing runs of whitespace into single spaces.
- For each candidate issue in the comparison set:
a. Compute title similarity: compare the incoming title to the candidate title. Consider them title-similar when they share the same core noun phrases or intent after stripping common prefixes like "bug:", "feature:", "[request]", emoji, and markdown formatting.
b. Compute description similarity: compare the key symptoms, error messages, reproduction steps, and requested behavior between the incoming and candidate descriptions. Ignore boilerplate template sections (e.g., "## Environment", "## Steps to Reproduce" headers with empty content) that do not carry diagnostic signal.
c. A candidate is a likely duplicate when both of the following hold:
- The titles convey the same problem, feature request, or question (not merely sharing a common keyword).
- The descriptions overlap on at least one substantive detail: a shared error message, the same failing behavior, the same requested capability, or an equivalent reproduction scenario.
- Rank candidates by overall similarity (title weight ≈ 40%, description weight ≈ 60%) and select the top matches.
- Only flag an issue as a duplicate when 2 or more existing issues are identified as likely duplicates. A single weak match is not sufficient — the evidence must be corroborated across multiple existing issues to reduce false positives.
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.
- 4d ago First seen · 57 lines · 46 tokens per session scan A c93ff1530bc1
dedupe-issue is a skill published in the GitHub repository warpdotdev/oz-for-oss (307 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 839 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…