skill-refactor

skill-refactor is a skill for Claude Code from navapbc/digital-service-orchestra. It costs 83 tokens per session (8,742 once invoked), scanned B, original, Apache-2.0.

A workflow for reviewing and improving an existing DSO skill. DSO is a project for managing development workflows, checks, and configuration.

In plain words
What is it for?
Use it to audit a skill, plan approved changes, move its scripts, update references, remove tests that only search prose, and reconcile related tickets.
Why use it?
It provides a structured way to make a skill clearer, shorter, and more reliable while keeping its documentation, tests, and related work aligned.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Good fit Use it to audit a skill, plan approved changes, move its scripts, update references, remove tests that only search prose, and reconcile related tickets.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/navapbc/digital-service-orchestra/skill-refactor
Install

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.

Any agent
npx skills add navapbc/digital-service-orchestra --skill skill-refactor
Clone the repo
git clone --depth 1 https://github.com/navapbc/digital-service-orchestra

Made for: Claude Code.

Wrote 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.

agentmods badge for skill-refactor

README.md
[![agentmods](https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/skill-refactor/github.svg)](https://agentmods.dev/skills/navapbc/digital-service-orchestra/skill-refactor)
Your own site
<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/skill-refactor"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/skill-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.

agentmods 80×15 button for skill-refactor

Your own site · 80×15
<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/skill-refactor"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/skill-refactor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,742 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00083 $0.08742
Opus 5 $0.00042 $0.04371
Sonnet 5 $0.00017 $0.01748
Haiku 4.5 $0.00008 $0.00874

Measured 12d ago against content hash eb9524be5141, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade B, and why

skill-refactor scanned grade B with 1 finding 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 12d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

grep -rln "${s}" plugins/dso/ .claude/ tests/ docs/ 2>/dev/null | grep -v "^plugins/dso/scripts/${s%.sh}\.sh$"
.claude/skills/skill-refactor/SKILL.md · 457 lines

How it starts

The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill Refactor

End-to-end token-efficiency and reliability pass on a DSO skill: review → approved plan → code/doc/test changes → ticket reconciliation → tessl review → committed result.

When to use

User signals: "review the X skill", "audit X", "can we optimize X?", "clean up X", "X is bloated", "X isn't reliable", or any request that implies critiquing a specific skill file and improving it.

Inputs

  • Skill name (bare, no dso: prefix) — e.g., architect-foundation, brainstorm.
  • The skill's SKILL.md at plugins/dso/skills/<name>/SKILL.md.
  • Any co-located phase files under plugins/dso/skills/<name>/phases/ or equivalent.

Workflow

The workflow is nine sequential phases. Do not skip. Phases A and B are synchronous with the user; Phases C–I execute autonomously once the plan is approved.

PA Critical review            → present findings
PB Remediation plan           → await explicit approval
PC Script relocation          → move skill-scoped scripts to shared sub-dir
PD Reference updates          → skill body, tests, docs
PE Change-detector test sweep → remove prose-grepping tests
PF Ticket reconciliation      → comment on open tickets affected
PG Renumbering                → renumber phases (A,B,C…) and steps (1,2,3…); update cross-skill refs
PH Tessl skill review         → run tessl skill review; act on valid+actionable findings
PI Commit                     → via COMMIT-WORKFLOW.md; surface review findings

White elephants: phrasings to remove

A white elephant in a skill file is a phrasing that is intended to enforce a rule but instead creates the very temptation it forbids. The phrase names a bypass shape (cost-pressure, urgency-pressure, perceptual judgment) and then tells the agent to ignore it. The naming makes the bypass salient. White elephants are the symmetric counterpart to the "Hard gates: compress, do not remove" rule below: hard gates are load-bearing enforcement that must be preserved (compress only); white elephants are bypass-narration that should be removed entirely (the rule's positive form already does the enforcement work).

Read the full file on GitHub · 457 lines

Changes

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.

  1. 12d ago First seen · 457 lines · 83 tokens per session scan B eb9524be5141

Subscribe to this mod's changes

skill-refactor is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed today), licensed Apache-2.0. It adds 83 tokens to every session and 8,742 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens