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 skills add saski/arnesto --skill xp-simple-design-refactorgit 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-simple-design-refactor)<a href="https://agentmods.dev/skills/saski/arnesto/xp-simple-design-refactor"><img src="https://agentmods.dev/badge/skills/saski/arnesto/xp-simple-design-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/saski/arnesto/xp-simple-design-refactor"><img src="https://agentmods.dev/badge/skills/saski/arnesto/xp-simple-design-refactor.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.00041 | $0.00299 |
| Opus 5.5 | $0.00016 | $0.00120 |
| Sonnet 5.5 | $0.00008 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
xp-simple-design-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 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.
What it actually says
Senior XP Developer — Maintainability & Simple Design Refactoring
Act as a Senior XP Developer applying XP Simple Design principles:
- Passes all tests
- Clearly expresses intent
- Contains no duplication
- Has the fewest elements needed
Task
-
Analyze the code and identify refactorings that:
- Reduce duplication and accidental complexity
- Improve naming, clarity, cohesion, and boundaries
- Simplify logic and reveal intent
- Align with small, incremental design
-
Prioritize refactors by ROI, considering:
- Impact on readability and future evolution
- Frequency of change
- Risk and complexity reduction
- Feasibility in small, safe steps
-
Implement the highest-ROI refactor using:
- Tiny, reversible changes
- A strong test safety net; add or refine tests if needed
- Strict adherence to simple design principles
-
Explain briefly:
- Why this refactor gives the highest ROI
- How it improves maintainability through simple design
- The next small improvement step
The final result must be simpler and more maintainable than before.
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 · 38 lines · 41 tokens per session scan A 4f403ebc127d
xp-simple-design-refactor is a skill published in the GitHub repository saski/arnesto (6 stars, last pushed 7d ago), licensed Unlicense. It adds 41 tokens to every session and 299 once invoked, about $0.0002 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-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.
doca-flow
DOCA Flow packet steering on NVIDIA NICs/DPUs, linked into a C application: match/action pipes, ports, representors, forwarding, hairpin, counters. Trigger on packet steering, classifier, rule-matching, representor, hairpin or 5-tuple-to-queue questions even when "DOCA Flow" is not named. Also covers pipe validation…
compute-sanitizer-diagnose-cuda-bugs
Detect and diagnose CUDA correctness bugs with NVIDIA Compute Sanitizer. Routes GPU memory errors, shared-memory data races, uninitialized-memory reads, and synchronization/barrier bugs to the right sub-tool (memcheck, racecheck, initcheck, synccheck) and explains how to build, run, and read the report. Use when…
doca-debug
Use this skill when the user is debugging any DOCA symptom — a build that won't compile, a link step that can't resolve a doca symbol, a runtime call returning DOCAERROR, a silent service or tool, or a stack trace / valgrind / core dump — and needs the layered ladder (install → version → build → link → runtime →…
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…