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 skills/dgouron/review-flow/refactoringnpx skills add DGouron/review-flow --skill refactoringgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/refactoring)<a href="https://agentmods.dev/skills/dgouron/review-flow/refactoring"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/refactoring.svg" alt="Measured on agentmods" 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.00048 | $0.01471 |
| Opus 5 | $0.00024 | $0.00736 |
| Sonnet 5 | $0.00010 | $0.00294 |
| Haiku 4.5 | $0.00005 | $0.00147 |
Grade A, and why
refactoring-mikado-strangler 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 5d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Large Scale Refactoring - Mikado & Strangler Fig
Persona
Read .claude/roles/senior-dev.md — adopt this profile and follow all its rules.
Activation
This skill activates for refactorings that exceed a TDD cycle scope:
- Architecture migration
- Library or framework replacement
- Splitting a monolithic module
- Pattern change (e.g., callbacks -> promises -> async/await)
- Bounded context restructuring
Choosing the method
| Criterion | Mikado | Strangler Fig |
|---|---|---|
| Old code stays functional during | No | Yes |
| Need to deliver incrementally | Difficult | Ideal |
| Complex dependencies to untangle | Ideal | Possible |
| Complete replacement of a system | Possible | Ideal |
Ask the user which method to use if it's not obvious.
Mikado Method
Principle
- Try the final goal directly
- Observe what breaks
- Revert immediately (no broken code left around)
- Note the discovered prerequisites in the graph
- Recurse on each prerequisite
- Implement the leaves of the graph (those with no dependencies)
Interactive workflow
Step 1: Initialization
MIKADO - Initialization
Main goal: [description]
Graph file: docs/mikado/[name]-graph.md
I will create the tracking file.
Shall we begin?
Create the graph file:
# Mikado Graph: [Goal]
## Status: IN PROGRESS
## Main goal
- [ ] [Goal description]
## Discovered prerequisites
(Fills in as attempts are made)
## Attempt history
(Log of attempts and discoveries)
Step 2: Attempt
MIKADO - Attempt
I will try: [goal or prerequisite]
Expected: [what should break]
Shall we try?
After validation:
- Attempt the modification
- Run
yarn test:run - Note EVERYTHING that breaks
- REVERT IMMEDIATELY with
git checkout .
Step 3: Analysis
MIKADO - Analysis
Attempt: [what we tried]
Result: [success / failure]
Errors encountered:
- [error 1] -> Prerequisite: [required action]
- [error 2] -> Prerequisite: [required action]
I'm updating the graph.
Which prerequisite do we tackle first?
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.
- 5d ago First seen · 295 lines · 48 tokens per session scan A 8952d1482852
refactoring-mikado-strangler is a skill published in the GitHub repository DGouron/review-flow (42 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 1,471 once invoked, about $0.0002 per session on Opus 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
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
verify-changes
Verify a code change in this repo before committing or opening a PR. Use after editing collector (backend), web (frontend), shared package, or the Go agent — picks the minimal sufficient check set per touched area.
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
monitor-webcams
Discover live webcams in a map viewport and resolve thumbnails or player URLs. Use when the user asks for visual context near a location, route, border, port, or city.
track-tariff-trends
Retrieve MFN applied tariff-rate timeseries for a reporting country — applied vs bound rates by year, plus the optional US effective tariff rate. Use when the user asks how a country's MFN tariffs have changed over time.
architecture-patterns
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…