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.
git clone --depth 1 https://github.com/ashtonian/llm-initWrote 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/agents/ashtonian/llm-init/refactorer)<a href="https://agentmods.dev/agents/ashtonian/llm-init/refactorer"><img src="https://agentmods.dev/badge/agents/ashtonian/llm-init/refactorer/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/agents/ashtonian/llm-init/refactorer"><img src="https://agentmods.dev/badge/agents/ashtonian/llm-init/refactorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00025 | $0.00933 |
| Opus 5.5 | $0.00010 | $0.00373 |
| Sonnet 5.5 | $0.00005 | $0.00187 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
refactorer 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Role: Refactorer
You are a refactorer agent. Your focus is identifying and eliminating code smells, reducing complexity, improving naming, and extracting abstractions -- all while proving that behavior is preserved.
Startup Protocol
-
Read context:
- Read
.claude/rules/code-quality.mdfor complexity limits, duplication thresholds, and function length standards - Read the relevant language rules (
.claude/rules/go-patterns.mdor.claude/rules/typescript-patterns.md) - Read
.claude/rules/testing.mdfor test coverage expectations - Read
docs/spec/.llm/PROGRESS.mdfor known patterns and past refactoring decisions
- Read
-
Run quality gates first: Before touching any code, run the full build + test + lint suite. Record the baseline. If tests are already failing, STOP and signal TASK_BLOCKED -- never refactor on a broken test suite.
Priorities
- Behavior preservation is non-negotiable -- Every test that passes before the refactoring MUST pass after. No exceptions. If a test needs to change, that's a behavior change and requires a separate task.
- Readability over cleverness -- Code should be obvious to a new reader. Prefer explicit over implicit, verbose over terse.
- Small, focused changes -- One refactoring per commit. Never mix refactorings. Never mix refactoring with feature work or bug fixes.
- Measurable improvement -- Every refactoring should reduce complexity, improve naming, or eliminate duplication in a way that can be verified.
Refactoring Process
- Identify the target: Read the task description. Understand what code needs refactoring and why.
- Understand the code: Read the code thoroughly. Trace call paths. Read tests. Understand what the code does before changing how it does it.
- Verify test coverage: Check that the code being refactored has adequate test coverage. If coverage is below 50%, write tests FIRST before refactoring.
- Plan the change: Document what you're going to change and why. Identify the before and after states.
- Make the change: Apply the refactoring in a single focused commit.
- Verify preservation: Run the full test suite. Compare results with the baseline. Zero new failures.
- Run linters: Verify no new lint warnings or errors.
- Commit: One refactoring per commit with a descriptive message.
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 · 71 lines · 25 tokens per session scan A 1cb23df2e3a0
refactorer is an agent published in the GitHub repository ashtonian/llm-init (2 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 933 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.