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/openshift/lightspeed-agentic-operator/find-duplicationnpx skills add openshift/lightspeed-agentic-operator --skill find-duplicationgit clone --depth 1 https://github.com/openshift/lightspeed-agentic-operatorWhat 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.00055 | $0.00937 |
| Opus 5 | $0.00028 | $0.00468 |
| Sonnet 5 | $0.00011 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
find-duplication 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Code Duplication
Detect duplicated or near-duplicate Go code and suggest consolidation candidates.
Rules
- Report findings, do not refactor. Refactoring is a separate task.
- Focus on production code (
controller/,api/,cmd/,cli/). Skip test duplication unless explicitly asked. - Group findings by severity: exact duplicates first, then near-duplicates.
- For each finding, state whether extraction is worth it or acceptable duplication.
Step 1: Determine Scope
Ask the user:
- Branch mode: only files changed in the current branch vs main.
- Full mode: scan the entire codebase.
For branch mode:
git diff --name-only upstream/main -- 'controller/' 'api/' 'cmd/' 'cli/' | grep '\.go$' | grep -v '_test\.go$'
For full mode, the target is controller/ api/ cmd/ cli/.
Step 2: Run dupl
Install and run dupl to find duplicate code blocks:
go install github.com/mibk/dupl@latest
dupl -threshold 15 <target>
-threshold 15 means at least 15 tokens of duplication. Lower values = more noise.
Review output and filter false positives:
- Import blocks (common imports are not duplication)
- Error constant declarations (repeated pattern is intentional)
- Single-line patterns (logging, error wrapping)
- Kubebuilder boilerplate (RBAC markers, webhook setup)
Step 3: Semantic Duplication Search
dupl only catches textual similarity. Also look for:
- Similar function signatures — functions with near-identical parameter lists doing similar work across different packages.
- Repeated error handling — same
if err != nil { return fmt.Errorf(...) }pattern with slight variations. - Copy-pasted reconciler logic — similar reconciliation patterns across different controllers.
- Duplicated struct definitions — similar structs in different packages (candidate for shared types).
Search for patterns:
# Find similar error wrapping
rg "fmt\.Errorf.*%w.*err\)" controller/ api/ cmd/ cli/ -A 1 -B 1
# Find similar reconciler patterns
rg "func.*Reconcile" controller/ -l
# Find similar generation helpers
rg "func Generate" controller/ -l
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 · 111 lines · 55 tokens per session scan A 4b455e4c5838
find-duplication is a skill published in the GitHub repository openshift/lightspeed-agentic-operator (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 55 tokens to every session and 937 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 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…