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 commands/mizchi/lsmcp/refactorgit clone --depth 1 https://github.com/mizchi/lsmcpWhat 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.00000 | $0.00610 |
| Opus 5 | $0.00000 | $0.00305 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Command
When I need to refactor TypeScript code in this project, follow these steps:
1. Analyze Current Code Structure
- Use
mcp__typescript__get_module_symbolsto understand module exports - Use
mcp__typescript__get_type_at_symbolto analyze type information - Use
mcp__typescript__find_referencesto find all usages before refactoring
2. Choose Appropriate Refactoring Tools
For Symbol Operations
- Rename: Use
mcp__typescript__rename_symbolinstead of Edit/MultiEdit - Delete: Use
mcp__typescript__delete_symbolto remove symbols and their references - Find usages: Use
mcp__typescript__find_referencesinstead of grep
For File Operations
- Move file: Use
mcp__typescript__move_fileinstead of bash mv - Move directory: Use
mcp__typescript__move_directoryfor entire directories
For Type Analysis
- Get type info: Use
mcp__typescript__get_type_at_symbol - Module analysis: Use
mcp__typescript__get_module_symbols - Scope analysis: Use
mcp__typescript__get_symbols_in_scope
3. Verify Changes
After refactoring:
- Run
pnpm typecheckto ensure no TypeScript errors - Run
pnpm lintto check code style - Run
pnpm testto verify functionality - Use
mcp__typescript__get_diagnosticsto check for issues
4. Common Refactoring Patterns
Extract Interface/Type
- Identify the type structure using
get_type_at_symbol - Create new type definition file
- Use
rename_symbolto update references
Move Module
- Use
move_fileormove_directory - Tool automatically updates all imports
- Verify with
get_diagnostics
Rename Across Project
- Use
find_referencesto see impact - Use
rename_symbolfor safe renaming - Check affected files with
git status
5. Best Practices
- Always use TypeScript MCP tools for semantic operations
- Never use text-based Edit/MultiEdit for refactoring
- Check references before deleting or moving
- Run tests after each refactoring step
- Commit frequently with descriptive messages
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 · 66 lines · 0 tokens per session scan A 5c6d2514a800
refactor is a command published in the GitHub repository mizchi/lsmcp (453 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 610 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.