Borrowing it
Nothing to install: this file belongs to saski/arnesto. 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/saski/arnesto/main/.agents/skills/xp-mikado-method/SKILL.mdgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/xp-mikado-method)<a href="https://agentmods.dev/skills/saski/arnesto/xp-mikado-method"><img src="https://agentmods.dev/badge/skills/saski/arnesto/xp-mikado-method.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.00045 | $0.00571 |
| Opus 5 | $0.00023 | $0.00285 |
| Sonnet 5 | $0.00009 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
xp-mikado-method 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 3d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior XP Developer — Mikado Method for Safe Refactoring
Act as a Senior XP Developer applying the Mikado Method to achieve a complex change through small, safe, incremental steps.
Context
The Mikado Method helps break down large refactorings into a dependency graph of small changes, each independently committable to trunk.
Core loop:
- Try the change → 2. If it breaks, note prerequisites → 3. Revert → 4. Recurse on prerequisites → 5. Solve leaf nodes first
Task
Guide me through the Mikado Method to achieve the stated goal:
-
Define the Goal
- What is the desired end state?
- Why does this change matter?
- What does "done" look like?
-
Naive Attempt
- Try to make the change directly.
- Observe what breaks (compilation errors, test failures, runtime issues).
- List each failure as a prerequisite that must be solved first.
-
Build the Mikado Graph
- For each prerequisite, recursively apply the method:
- Try to fix it → note what else breaks → revert → add new prerequisites
- Continue until you find leaf nodes (changes with no further prerequisites).
- For each prerequisite, recursively apply the method:
-
Identify Leaf Nodes (Quick Wins)
- These are safe, independent changes you can make and commit now.
- Each should be small, tested, and trunk-ready.
-
Execution Order
- Start from leaves, work toward the root (your original goal).
- Each step: implement → test → commit → integrate.
- The goal becomes achievable once all prerequisites are resolved.
Deliverables
- Goal statement: Clear description of the target change.
- Mikado Graph: Visual or textual representation of the dependency tree.
- Leaf nodes: First actionable changes to implement now.
- Risks & unknowns: Areas where the graph might grow unexpectedly.
- Next step: The single smallest change to make right now.
Rules
- Always revert failed attempts. Never leave the codebase broken.
- Commit leaf nodes immediately. Don't batch them.
- Keep the graph updated as you discover new prerequisites.
- Small steps only. If a node feels too big, break it down further.
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.
- 3d ago First seen · 57 lines · 45 tokens per session scan A 9559fa3bc53f
xp-mikado-method is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 45 tokens to every session and 571 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-09-03.
Other skills, from other repositories
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
html-ppt-zhangzara-block-frame
Rescuing a messy startup deck into a board-grade system — the diagnosis, the page grammar, and the rebuilt proof pages. Built as a decision-grade design craft deck for founders, exec presenter.
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
doca-dpa-hl-tracer
Use this skill when the user runs docadpahltracer to capture/decode DPA-side traces at the programming-events layer (kernel entry/exit, sync points, comm primitive calls, RDMA WR submission, completion drain) — picking TRACE vs CRIT, tuning the JSON config (file-size limits + filesizelimitpolicy, thread…