What is refactor-design-report?

A skill for producing a practical engineering report about a refactor or implementation. It starts from the actual code and describes the current problem, target behaviour, changes, validation, order of work, and acceptance criteria.

It helps document backend and frontend changes, API or UI contract problems, architecture issues, test plans, and implementation steps. If requested, it can save the report in the project's documentation.

It turns scattered bugs, design concerns, or missing protections into a written plan that developers can implement and review.

refactor-design-report — Skill for Codex by penwyp/ClaudePreference

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 penwyp/ClaudePreference --skill refactor-design-report

Clone the repo

git clone --depth 1 https://github.com/penwyp/ClaudePreference

Made for: Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/penwyp/claudepreference/refactor-design-report/github.svg)](https://agentmods.dev/skills/penwyp/claudepreference/refactor-design-report)

Your own site

<a href="https://agentmods.dev/skills/penwyp/claudepreference/refactor-design-report"><img src="https://agentmods.dev/badge/skills/penwyp/claudepreference/refactor-design-report/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/penwyp/claudepreference/refactor-design-report"><img src="https://agentmods.dev/badge/skills/penwyp/claudepreference/refactor-design-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,083 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00092	$0.01083
Opus 5.5	$0.00037	$0.00433
Sonnet 5.5	$0.00018	$0.00217
Haiku 4.5	$0.00009	$0.00108

Measured 2mo ago against content hash fc3b6f7548dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

refactor-design-report 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.

skills/refactor-design-report/SKILL.md · 128 lines

How it starts

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

Refactor Design Report

Purpose

Create a durable engineering report that turns concrete problems into an executable design. Ground the report in the current code and contracts first, then describe the target model, backend changes, frontend changes, validation strategy, implementation order, and acceptance criteria.

Workflow

Normalize the request.
- Extract the concrete issues, desired behavior, affected user flows, and any stated constraints.
- Separate current defects from desired future capabilities.
- If the user says to persist the result, write a focused design document in the appropriate docs location; otherwise provide the report in the reply.
Locate the real implementation.
- Find entry points before designing: API definitions, handlers, service methods, data models, workflow runners, frontend request builders, UI components, tests, and docs.
- Prefer real call paths over keyword-level guesses.
- Identify what is already implemented, what is only documented, and what is missing.
Define the target semantics.
- Name the core concepts and states precisely.
- State invariant rules as hard requirements, not suggestions.
- Resolve ambiguous user-facing terms into exact technical meanings.
- Decide which behavior belongs in backend hard validation, frontend guidance, workflow preflight, and tests.
Design the backend.
- Cover API/proto/schema changes, storage changes, service validation, workflow/runtime changes, error types, idempotency, locking, and retry behavior.
- Put hard safety rules in backend paths that cannot be bypassed by the UI.
- Include both precheck-time and execution-time validation when state can change between submit and execution.
Design the frontend.
- Cover UI state, available actions, disabled states, warnings, confirmations, request shape, response handling, and stale precheck protection.
- Ensure user wording matches the actual backend semantics.
- Prevent users from selecting impossible or unsafe combinations; still rely on backend validation as final authority.

Read the full file on GitHub · 128 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 317 B

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.

2mo ago First seen · 128 lines · 92 tokens per session scan A fc3b6f7548dc

Subscribe to this mod's changes

refactor-design-report is a skill published in the GitHub repository penwyp/ClaudePreference (136 stars, last pushed 5mo ago), licensed MIT. It adds 92 tokens to every session and 1,083 once invoked, about $0.0004 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.

Planning

refactor-design-report next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
refactor-design-reportpenwyp/ClaudePreference	Skill	136	5mo ago	MIT	A	92	Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	315k	5d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code