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/event4u-app/agent-config/code-refactoringnpx skills add event4u-app/agent-config --skill code-refactoringgit clone --depth 1 https://github.com/event4u-app/agent-configWhat 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.00044 | $0.03126 |
| Opus 5 | $0.00022 | $0.01563 |
| Sonnet 5 | $0.00009 | $0.00625 |
| Haiku 4.5 | $0.00004 | $0.00313 |
Grade A, and why
code-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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
refactorer
When to use
Use this skill when renaming, moving, extracting, or restructuring code — any change that may have downstream effects on callers, interfaces, tests, documentation, or API contracts.
Do NOT use when:
- New feature development (use
feature-planningskill) - Bug fixes that don't involve restructuring (use
bug-analyzerskill)
Before refactoring
- Read the agent docs — check
agents/reference/docs/andagents/settings/contexts/for the area you're refactoring. For modules, also read the project's module-docs directory (path varies by stack — Laravel:app/Modules/{Module}/agents/; Nx:apps/{app}/docs/; mono-repo: per-packagedocs/). See theproject-docsskill for the mapping. - Understand the scope — what exactly needs to change and why?
- Find ALL references — use
codebase-retrievalandviewwithsearch_query_regexto find every caller, implementation, test, and configuration that references the code being changed. If the change is to a closed set — an enum, union, literal type, state machine, role or permission set — identifier search is not enough: the consumers that break are the ones that never name the type. Search by shape as well (switch/match/ if-chains over it, lookup tables keyed by it, validators, serializers, schemas, fixtures, translation keys) and classify each as exhaustive, deliberate fallback, or missing case. Procedure:downstream-changes-mechanics. - Map the impact — create a list of all files that will need changes.
- Decide the verdict, if the refactor is a de-duplication — see the safe-abstraction gate below. An extraction with no recorded verdict is a guess about whether two things are the same thing.
- Present the plan — show the user what will be affected before starting.
Safe-abstraction gate — before merging two things into one
This skill performs extractions; it is therefore the place that decides whether one should happen. A wrong abstraction costs more than the duplication it replaced, because the duplication is visible and the wrong abstraction grows caller flags until nobody can remove it. Ask, before moving any code:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 256 lines · 44 tokens per session scan A 5836834a455c
code-refactoring is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 3,126 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
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the eleven operating disciplines (prepaid billing, quote-before-spend, retryable…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
human-approval
Request human approval before performing a SAFETY-CRITICAL, IRREVERSIBLE, or SCOPE-EXPANDING action — submit a structured context (action, scope, risk, consequence) plus options, then STOP the current turn. The platform redispatches the agent after the human decides. NEVER use for routine deliverables (writing docs /…