Borrowing it
Nothing to install: this file belongs to rsalmn/ExtremeRouter. 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/rsalmn/ExtremeRouter/main/.agents/skills/extreme-router-refactor/SKILL.mdgit clone --depth 1 https://github.com/rsalmn/ExtremeRouterWrote 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/rsalmn/extremerouter/extreme-router-refactor)<a href="https://agentmods.dev/skills/rsalmn/extremerouter/extreme-router-refactor"><img src="https://agentmods.dev/badge/skills/rsalmn/extremerouter/extreme-router-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/rsalmn/extremerouter/extreme-router-refactor"><img src="https://agentmods.dev/badge/skills/rsalmn/extremerouter/extreme-router-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.00078 | $0.01244 |
| Opus 5.5 | $0.00031 | $0.00498 |
| Sonnet 5.5 | $0.00016 | $0.00249 |
| Haiku 4.5 | $0.00008 | $0.00124 |
Grade A, and why
extreme-router-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 2mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Refactoring & Review Expertise
You are an expert in identifying and resolving technical debt, code smells, and architectural issues.
Refactoring Philosophy
Never stop after solving the visible issue.
Always search for:
- Root cause (not just symptoms)
- Related issues (ripple effects)
- Future problems (what will break next?)
- Architectural improvements (how to prevent this class of issue)
Think two steps ahead. Fix the problem, then fix the system that allowed the problem.
Code Review Checklist
When reviewing code, check for:
Correctness
- Logic errors
- Edge cases (null, undefined, empty arrays, zero values)
- Error handling (what happens when things fail?)
- Race conditions (async/await, concurrent updates)
- Data validation (trust boundaries)
Security
- Input sanitization (SQL injection, XSS, command injection)
- Authentication/authorization checks
- Secret exposure (hardcoded keys, logs, error messages)
- CORS/CSRF protection
- Rate limiting
Performance
- Unnecessary re-renders (React components)
- Missing memoization (expensive computations)
- N+1 queries (database access patterns)
- Missing indexes (database queries)
- Large bundle imports (tree-shaking opportunities)
- Synchronous operations that should be async
Maintainability
- Code duplication (DRY violations)
- Magic numbers/strings (use constants)
- Deep nesting (extract functions/components)
- Long functions (>50 lines = refactor)
- Complex conditionals (extract to named variables)
- Poor naming (unclear intent)
Architecture
- Separation of concerns (UI vs business logic)
- Dependency direction (should flow inward)
- Coupling (tight vs loose)
- Cohesion (related things together)
- Abstraction level (too high-level or too low-level)
Refactoring Process
When refactoring existing code:
- Explain what's wrong — be specific, cite code
- Explain why it's wrong — impact on maintainability/performance/security
- Show the impact — what happens if we don't fix it?
- Propose the solution — how to improve it
- Rewrite it cleanly — provide the improved code
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.
- 2mo ago First seen · 175 lines · 78 tokens per session scan A 96bc5f2fa26a
extreme-router-refactor is a skill published in the GitHub repository rsalmn/ExtremeRouter (49 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,244 once invoked, about $0.0003 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
human-review
Produce a plain-English review of the files you just edited and gate the changes behind an explicit Approve/Undo choice. Use when the Stop hook from the human-review-skill plugin asks for a review (you'll see a prompt referencing an edit log), OR when the developer's most recent message is "1", "2", "approve", or…
code-reviewer
Perform thorough code reviews — bugs, security issues, performance bottlenecks, style violations, and architectural concerns.
security-auditor
Audit code for security vulnerabilities — OWASP Top 10, injection flaws, auth issues, secrets exposure, and dependency risks.
code-review
Comprehensive code review assistant that analyzes code quality, security, and best practices.
implement-audit
Adversarial review of freshly-built code — find what was missed, what's inconsistent, what breaks. The single code reviewer for the loop. Auto-fired by /implement (phase-4.7); standalone-callable after any substantial change. Writes an implement-audit: line into the report.
spec-audit
Adversarial pre-review of any freshly-written or materially-rewritten SPEC or spec folder, running reviewer consensus (correctness) plus the spirit-check agent (fidelity to the user's verbatim ask — spec.md's Input and Clarifications, or a single-file SPEC's § 0 / § 0a — and to the behavior contract) in one pass and…