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/bugrabilge/bilge-development-kit/refactornpx skills add bugrabilge/bilge-development-kit --skill refactorgit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWhat 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.00048 | $0.01018 |
| Opus 5 | $0.00024 | $0.00509 |
| Sonnet 5 | $0.00010 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
refactor 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/refactor - Systematic Refactoring
$ARGUMENTS
Purpose
This command performs safe, systematic refactoring using the code-archaeologist agent with support from domain specialists.
Sub-commands
/refactor [file/dir] - Analyze and refactor target
/refactor analyze - Analysis only, no changes
/refactor extract - Extract functions/components
/refactor rename - Rename across codebase
/refactor modernize - Update to modern patterns
/refactor types - Add/improve TypeScript types
Behavior
When /refactor is triggered:
Phase 1: Analysis (NO CODE CHANGES)
-
Invoke
code-archaeologistagent- Map the code structure
- Identify anti-patterns and tech debt
- Assess risk of changes
- Find dependencies that will be affected
-
Invoke
explorer-agent(if needed)- Trace usage across codebase
- Find all consumers/dependents
-
Present analysis to user
## Refactoring Analysis: [Target] ### Current State - Complexity: [Low/Medium/High] - Test Coverage: [X%] - Dependencies: [List of affected files] ### Proposed Changes 1. [Change with rationale] 2. [Change with rationale] ### Risk Assessment | Risk | Mitigation | |------|------------| | [Risk] | [How to mitigate] | ### Estimated Impact - Files changed: X - Lines modified: ~Y Proceed? (Y/N)
Phase 2: Safety Net (After Approval)
- Invoke
test-engineer- Write characterization tests (capture current behavior)
- Verify tests pass on current code
- These tests protect against regression
Phase 3: Refactor (Sequential, Verified)
-
Apply changes incrementally
- One refactoring at a time
- Run tests after each change
- If tests fail, revert and investigate
-
Common refactoring operations:
Operation When to Use Extract function/method Long functions (>30 lines) Extract component Component does too many things Rename Unclear or misleading names Move/reorganize Wrong file location Simplify conditionals Nested if/else pyramids Replace patterns Class -> Hook, Callback -> Promise Add types anytypes, missing interfaces
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 · 167 lines · 48 tokens per session scan A 7b8ea192066f
refactor is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 1,018 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…