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 skills add marcoemrich/agentic_coding_lab --skill refactorgit clone --depth 1 https://github.com/marcoemrich/agentic_coding_labWrote 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/marcoemrich/agentic_coding_lab/refactor)<a href="https://agentmods.dev/skills/marcoemrich/agentic_coding_lab/refactor"><img src="https://agentmods.dev/badge/skills/marcoemrich/agentic_coding_lab/refactor/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/marcoemrich/agentic_coding_lab/refactor"><img src="https://agentmods.dev/badge/skills/marcoemrich/agentic_coding_lab/refactor.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.00022 | $0.02408 |
| Opus 5.5 | $0.00009 | $0.00963 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (13 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 2,408 once invoked, about $0.0001 per session on Opus 5.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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…