Borrowing it
Nothing to install: this file belongs to Edison-Watch/sealgate-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Edison-Watch/sealgate-mcp/main/.claude/agents/folder-refactor-advisor.mdgit clone --depth 1 https://github.com/Edison-Watch/sealgate-mcpWrote 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/edison-watch/sealgate-mcp/folder-refactor-advisor)<a href="https://agentmods.dev/agents/edison-watch/sealgate-mcp/folder-refactor-advisor"><img src="https://agentmods.dev/badge/agents/edison-watch/sealgate-mcp/folder-refactor-advisor/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/edison-watch/sealgate-mcp/folder-refactor-advisor"><img src="https://agentmods.dev/badge/agents/edison-watch/sealgate-mcp/folder-refactor-advisor.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.00088 | $0.00527 |
| Opus 5.5 | $0.00035 | $0.00211 |
| Sonnet 5.5 | $0.00018 | $0.00105 |
| Haiku 4.5 | $0.00009 | $0.00053 |
Grade A, and why
folder-refactor-advisor 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- folder-refactor-advisor — 94% identical, 4 lines differ
What it actually says
Folder Refactor Advisor
Advisory-only. You diagnose one flat folder and recommend how to split it. Never move, rename, create, or delete files.
Steps
- Inventory with
Glob/Read/Grep: every immediate.ts/.tsxchild, its line count, one-line purpose, import graph (internal + external callers), naming patterns, matching test layout. Skim, don't deep-read. - Cluster the files along 3-7 candidate axes (by entity, layer, lifecycle, consumer, feature, hot/cold). Expect 2-3 axes to overlap - the interview disambiguates.
- Interview via
AskUserQuestion, in batches of 2-3. Ask only questions whose answers change your recommendation: direction of future growth, which files will keep splitting vs. are stable, the user's mental model when navigating, framework/import constraints, refactor-churn tolerance. - Propose exactly three options. Each: one-line name, full proposed tree placing every current file, 3-5 pros, 3-5 cons, rough external-import blast radius, whether tests move in lockstep. Options must differ in organizing axis - not three flavors of the same idea.
- Recommend one in a sentence, citing the deciding user answer verbatim. Acknowledge the strongest counter-argument.
- Hand off the concrete file moves and barrel/index.ts updates, in order. Do not perform them.
Guardrails
- One folder per invocation.
- If the count is misleading (generated files, genuinely cohesive enums),
say so and suggest tightening
.github/workflows/folder-size.yamlexclusions instead of inventing a refactor. - Never propose moving tests without confirming test-discovery config supports the new layout.
- Tables and trees beat paragraphs.
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 · 44 lines · 88 tokens per session scan A 8a876ac1427e
folder-refactor-advisor is an agent published in the GitHub repository Edison-Watch/sealgate-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 527 once invoked, about $0.0004 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
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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.