Borrowing it
Nothing to install: this file belongs to tuanductran/hr-skills. 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/tuanductran/hr-skills/main/.agents/skills/dry-refactoring/SKILL.mdgit clone --depth 1 https://github.com/tuanductran/hr-skillsWrote 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/tuanductran/hr-skills/dry-refactoring)<a href="https://agentmods.dev/skills/tuanductran/hr-skills/dry-refactoring"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/dry-refactoring/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/tuanductran/hr-skills/dry-refactoring"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/dry-refactoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01234 |
| Opus 5 | $0.00026 | $0.00617 |
| Sonnet 5 | $0.00010 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
dry-refactoring 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dry-refactoring
Guided workflow to eliminate copy-paste duplication in packages/* TypeScript source. Use after jscpd has produced a clone list.
Prerequisites
Run jscpd first — see jscpd for the exact command this repo uses:
bunx jscpd@5 packages --reporters ai --format typescript
Workflow
- Run jscpd, scoped to
packages/only (neverskills/, see thejscpdskill for why). - Parse each clone line to identify the two duplicated locations (file + line range).
- Read both code fragments and understand what they do — don't refactor blind.
- Decide the refactor target using the placement rules below.
- Extract the shared logic; update all call sites, not just the two jscpd reported.
- Run
bun run typecheckandbun run test(repo-wide or--filterto the affected package — seeturbo). - Re-run jscpd to confirm the clone is gone.
- Repeat, highest-impact cluster first (most repeated pattern, not just the first line in the report).
Where extracted code goes in this repo
This repo separates code by surface and domain under
packages/hr-skills/src/cli/, packages/hr-skills-build/src/client/,
packages/hr-skills-build/src/server/, packages/hr-skills-ref/src/client/,
and packages/hr-skills-ref/src/server/. Follow that structure — don't dump
extracted helpers into whichever file happens to be open:
- Duplicated logic used by 2+ files in the same domain folder (e.g. two files under
src/server/validation/) → new file in that same folder, e.g.src/server/validation/security-helpers.ts, imported by both. - Duplicated logic used across domain folders (e.g.
src/server/build/*andsrc/server/evaluation/*) →src/server/shared/, alongside the existingshared/constants.ts,shared/helpers.ts,shared/schema.ts,shared/types.ts. - Duplicated logic across packages (
hr-skills-buildandhr-skills-refboth define it) → do not create a third copy in either package. Prefer keeping a single canonical definition in the package it conceptually belongs to (hr-skills-reffor skill-file parsing primitives,hr-skills-buildfor build/registry/CLI concerns) and importing it from the other, or promote it to a small shared internal package if both genuinely need to own it independently. Never resolve this by copy-pasting into a third location. - Intentional client/server duplication → each public surface must remain self-contained. If sharing a module would create a client/server import edge, keep separate surface-local implementations and test both surfaces instead.
- Constants → their own
constants.tsin the relevant folder; don't fold them into a file that already holds functions or types. - Types/interfaces → their own
types.ts(or*.types.tsiftypes.tsalready exists and would grow unrelated concerns) in the relevant folder — never appended to a functions file "for now."
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 Changed · +7 lines 5e2f37b55515
- 12d ago First seen · 68 lines · 51 tokens per session scan A 2219660f148a
dry-refactoring is a skill published in the GitHub repository tuanductran/hr-skills (57 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,234 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…