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-skills/github-issue-dedupenpx skills add warpdotdev/oz-skills --skill github-issue-dedupegit clone --depth 1 https://github.com/warpdotdev/oz-skillsWhat 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.00038 | $0.00816 |
| Opus 5 | $0.00019 | $0.00408 |
| Sonnet 5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
github-issue-dedupe 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 2d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Duplicate Issue Detection
Find duplicate GitHub issues using multi-strategy search. Can be run manually or automated via GitHub Actions.
Workflow
1. Gather Issue Context
Extract key information from the target issue:
- Issue number and title
- Full body content
- Error messages or stack traces
- Keywords and technical terms
- Symptoms or behavior descriptions
2. Search Strategy
Use gh to search for related issues using multiple strategies:
- Keyword search from title and body
- Search for similar error messages
- Look for similar symptoms
3. Candidate Inspection
For each potential duplicate:
- View full issue with
gh issue view <number> - Compare:
- Root cause (same underlying problem?)
- Symptoms (identical behavior?)
- Error messages (exact match or very similar?)
- Affected components (same area of code?)
High confidence indicators:
- Identical error messages
- Same reproduction steps
- Same root cause with different descriptions
- One issue references the other
Low confidence (not duplicates):
- Similar symptoms but different causes
- Related but independent bugs
- Same component but different behaviors
4. Report Findings
If duplicates found:
Post comment on target issue:
gh issue comment <number> --body "This is potentially a duplicate of #123 and #456."
Format rules:
- Single duplicate: "This is potentially a duplicate of #123."
- Two duplicates: "This is potentially a duplicate of #123 and #456."
- Three+ duplicates: "This is potentially a duplicate of #123, #456, and #789."
Only comment if high confidence (90%+ certain). When uncertain, do nothing.
Examples
Example 1: Clear Duplicate
Target Issue #150:
Title: "Dropdown menu stays open on mobile Safari"
Body: Clicking menu items doesn't close dropdown on iOS
Search process:
gh issue list --search "dropdown mobile safari"
gh issue list --search "menu doesn't close"
gh issue view 87 # Found similar issue
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.
- 2d ago First seen · 138 lines · 38 tokens per session scan A 27ba2736754a
github-issue-dedupe is a skill published in the GitHub repository warpdotdev/oz-skills (823 stars, last pushed 17d ago), licensed MIT. It adds 38 tokens to every session and 816 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
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.