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/dbinky/dbinky-skill-set/curating-codenpx skills add dbinky/dbinky-skill-set --skill curating-codegit clone --depth 1 https://github.com/dbinky/dbinky-skill-setWhat 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.00041 | $0.00463 |
| Opus 5 | $0.00020 | $0.00231 |
| Sonnet 5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
curating-code 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.
What it actually says
Codebase Curation
Analyze a codebase (or targeted path) for vibe-coding cruft using four parallel specialist agents. Consolidates findings into a prioritized report, lets you select which issues to address, and implements the fixes.
Usage
/curating-code # Sweep the entire codebase
/curating-code src/ # Curate a specific directory
/curating-code lib/auth.ts # Curate a specific file
Pipeline
Scope & Detect → [Dead Code Hunter | Complexity Reducer | Duplication Consolidator | Consistency Enforcer] → Consolidate → Report → Select → Implement
Specialists
| Agent | Finding Prefix | Focus |
|---|---|---|
| Dead Code Hunter | DC- |
Unused functions, unreachable branches, orphaned files, stale imports |
| Complexity Reducer | CX- |
Over-abstraction, deep nesting, convoluted control flow, god functions |
| Duplication Consolidator | DU- |
Near-identical blocks, copy-paste patterns, consolidation opportunities |
| Consistency Enforcer | CN- |
Divergent patterns, mixed conventions, conflicting approaches |
Process
Read and follow the orchestrator instructions exactly:
Orchestrator file: agents/curation-orchestrator.md (relative to this plugin's root)
The orchestrator will:
- Verify git repository and resolve target scope
- Detect languages and frameworks, load applicable curation rule files
- Dispatch all four specialist agents in parallel
- Consolidate findings: deduplicate, cross-reference, resolve conflicts, assign tiers
- Present a categorized curation report (Critical / Important / Consider / Cosmetic)
- Let you select which findings to address (by tier or individually)
- Dispatch the curator implementer for selected fixes
IMPORTANT: Read the orchestrator file using the path ${CLAUDE_PLUGIN_ROOT}/agents/curation-orchestrator.md and follow it exactly.
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 · 49 lines · 41 tokens per session scan A dce05267ac7e
curating-code is a skill published in the GitHub repository dbinky/dbinky-skill-set (5 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 463 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-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…