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/davidruzicka/mcp4openapi/prevent-generated-code-duplicationnpx skills add davidruzicka/mcp4openapi --skill prevent-generated-code-duplicationgit clone --depth 1 https://github.com/davidruzicka/mcp4openapiWhat 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.00028 | $0.00376 |
| Opus 5 | $0.00014 | $0.00188 |
| Sonnet 5 | $0.00006 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
prevent-generated-code-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 yesterday.
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
Goal
Prevent divergence and maintenance risk by consolidating duplicated logic created by code generation or by mixing generated and hand-written code.
When to Use
- New generated files duplicate logic already present in the project.
- Generated output duplicates existing generated modules.
- Generated code and hand-written code implement equivalent validation/parsing/mapping/error handling.
- Reviews identify repeated blocks after schema/code generation.
Rules
- Treat generated-vs-existing duplication as high-priority technical debt and resolve in the same change when feasible.
- Prefer extraction to shared runtime modules (helpers/utilities/services), not copy-paste edits across multiple generated files.
- Keep codegen outputs thin: delegate behavior to shared functions where possible.
- If generator templates are available, fix duplication at template/source level first.
- If template-level fix is not feasible, add a small shared abstraction and route both generated and existing code through it.
- Preserve behavior and public interfaces; avoid broad architecture changes unless required.
- Validate with lint, typecheck, and relevant tests after deduplication.
Workflow
- Identify duplicate blocks and classify:
- generated <-> generated
- generated <-> hand-written
- Pick dedup strategy:
- template fix (preferred)
- shared helper/module extraction
- Refactor call sites to shared implementation.
- Remove duplicated code paths.
- Run verification (lint + typecheck + tests).
- Document the dedup decision in change summary.
Output Pattern
- Duplicates found (files + intent).
- Chosen dedup strategy and why.
- Refactored shared location.
- Verification results.
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.
- yesterday First seen · 41 lines · 28 tokens per session scan A e76b1b6060e3
prevent-generated-code-duplication is a skill published in the GitHub repository davidruzicka/mcp4openapi (0 stars, last pushed 14d ago), licensed MIT. It adds 28 tokens to every session and 376 once invoked, about $0.0001 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…