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/marcoemrich/agentic_coding_lab/refactornpx skills add marcoemrich/agentic_coding_lab --skill refactorgit clone --depth 1 https://github.com/marcoemrich/agentic_coding_labWhat 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.00022 | $0.02408 |
| Opus 5 | $0.00011 | $0.01204 |
| Sonnet 5 | $0.00004 | $0.00482 |
| Haiku 4.5 | $0.00002 | $0.00241 |
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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Refactor Phase
You are now in the Refactor Phase of TDD. Follow these instructions to improve the code while keeping tests green.
Your Mission
Guide developers through the Refactor phase of TDD by helping them:
- MUST attempt at least one refactoring - mandatory, not optional
- Apply the Four Rules of Simple Design in priority order
- Use Absolute Priority Premise (APP) to measure code improvements
- Improve code quality while keeping all tests green
- Document refactoring decisions and mass calculations
- If no improvement is possible, explicitly document why
Context: $ARGUMENTS
Refactor Phase Rules
- Mandatory refactoring attempt: MUST try at least one improvement
- Tests must stay green: Never break passing tests
- Apply Simple Design Rules: In priority order (1 -> 2 -> 3 -> 4)
- Calculate APP mass: Before and after refactoring
- Document decisions: Explain improvements or why none were possible
- Naming is first priority: Evaluate if function name still fits its purpose
Simple Design Rules (Priority Order)
Rule 1: Tests Pass
- Highest priority - never compromise working code
- All tests must pass before and after refactoring
- If tests fail, revert and try different approach
Rule 2: Reveals Intent
- Second priority - clarity trumps everything else (including APP)
- Use meaningful names for variables, functions, classes
- Structure code to be self-documenting
- Prefer explicit over clever code
- Naming Evaluation (First Refactoring Priority):
- Ask: "Does this name clearly describe what the function actually does based on all tests we have so far?"
- Ask: "Has the function's purpose become clearer/more specific through the latest test?"
- Rename if the name doesn't capture the current full intent
- Especially critical when new functionality changes the nature of what the function does
Rule 3: No Duplication (DRY)
- Third priority - extract common functionality
- Look for obvious and conceptual duplication
- Knowledge should have single representation
- Balance with Rule 2: If DRY hurts clarity, choose clarity
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 · 328 lines · 22 tokens per session scan A 7bda94ec9601
refactor is a skill published in the GitHub repository marcoemrich/agentic_coding_lab (11 stars, last pushed 15d ago), licensed MIT. It adds 22 tokens to every session and 2,408 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-30.
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…