refactor-classification-policy

refactor-classification-policy is a skill for Claude Code from babyworm/rtl-agent-team. It costs 21 tokens per session (406 once invoked), scanned A, original, MIT.

A guide for deciding which RTL refactoring changes are safe, restricted, or prohibited based on their possible effect on behavior and design contracts.

In plain words
What is it for?
Use it when reviewing or approving RTL cleanup, module restructuring, testbench changes, or constraint-file changes.
Why use it?
It prevents cleanup work from silently changing state machines, pipeline timing, reset behavior, clock-domain crossings, or interfaces.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the rtl-agent-team plugin — 47 skills, 99 agents, 6 hooks shipped together

Good fit Use it when reviewing or approving RTL cleanup, module restructuring, testbench changes…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/babyworm/rtl-agent-team/refactor-classification-policy
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 babyworm/rtl-agent-team --skill refactor-classification-policy
Clone the repo
git clone --depth 1 https://github.com/babyworm/rtl-agent-team

Made for: Claude Code.

Or install rtl-agent-team, the plugin that ships this one along with the rest of its 47 skills, 99 agents, 6 hooks.

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 refactor-classification-policy

README.md
[![agentmods](https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/refactor-classification-policy.svg)](https://agentmods.dev/skills/babyworm/rtl-agent-team/refactor-classification-policy)
Your own site
<a href="https://agentmods.dev/skills/babyworm/rtl-agent-team/refactor-classification-policy"><img src="https://agentmods.dev/badge/skills/babyworm/rtl-agent-team/refactor-classification-policy.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 406 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00406
Opus 5 $0.00010 $0.00203
Sonnet 5 $0.00004 $0.00081
Haiku 4.5 $0.00002 $0.00041

Measured 3d ago against content hash 138e20814f1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

refactor-classification-policy 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.

skills/refactor-classification-policy/SKILL.md · 61 lines

What it actually says

Refactor Policy

Refactor Classes

  • SAFE: behavior-preserving cleanup with no interface/timing contract impact
  • RESTRICTED: likely behavior-preserving but affects structure or test assumptions
  • PROHIBITED: behavior/spec contract may change

SAFE (auto-apply allowed)

  • Naming/format consistency fixes
  • Dead code removal
  • Local duplication cleanup with equivalent logic
  • Comment/documentation synchronization

RESTRICTED (approval or explicit orchestrator permit)

  • Significant module decomposition/merge
  • Testbench structure reshaping affecting check points
  • Constraint file reorganization without semantic change proof

PROHIBITED (manual approval required)

  • FSM semantic changes
  • Pipeline latency/stage changes
  • CDC strategy changes
  • Interface contract changes
  • Reset behavior semantics changes

Pass/Fail Gate

  • FAIL: any prohibited change applied without approval
  • FAIL: equivalence confidence not demonstrated for SAFE/RESTRICTED changes
  • PASS: only SAFE changes applied and mandatory recheck passed

Escalation

  • Any ambiguity about behavior equivalence: escalate as RESTRICTED
  • Any proposal touching interface/timing contract: escalate before edit
  • Repeated recheck fail after 2 attempts: stop and hand off with root-cause note

Output Format

Use the following refactor execution report:

# Refactor Execution Report
- Scope: module|block|top
- Verdict: PASS | FAIL

## Planned Changes
| ID | Class | Target | Rationale | Approval Required |
|---|---|---|---|---|

## Applied Changes
| ID | Files | Summary | Risk |
|---|---|---|---|

## Blocked/Deferred
- [approval-required or risky items]
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. 3d ago First seen · 61 lines · 21 tokens per session scan A 138e20814f1c

Subscribe to this mod's changes

refactor-classification-policy is a skill published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 13d ago), licensed MIT. It adds 21 tokens to every session and 406 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

qa-review

QA review for code changes — test coverage analysis, edge case identification, test plan generation, regression detection, test health tracking over time.

suyoumo/ClawProBench · 30 tokens

flutter-mcp-boundary-audit

Generic contract/schema boundary audit across authoring, discovery, validation, and execute—detecting split-brain between listings and invoke paths, gateway divergence, and permissive placeholders. Use when changing tool registration, RPC/plugin registries, dynamic tools, MCP or WebMCP surfaces, CLI exec aliases…

Arenukvern/mcp_flutter · 92 tokens

readable-verilog-generator

Use when creating, writing, reviewing, annotating, repairing, refactoring, or validating readable Verilog RTL, including synthesizable Verilog-2001 .v files, existing-RTL analysis, semantic comment annotation, testbench scaffold planning, ASIC-quality review, local or remote Vivado/xsim validation, evidence-backed…

Eriemon/verilog-generator · 77 tokens

fresh-eyes-loop

A repeatable quality-review process using two independent agents: one reviews and verifies, while the other fixes issues. P0 and P1 mean the highest-severity problem levels.

KongFangXun/sofagent · 58 tokens

aster-review-ci

Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers aster review --pr, --json, --stream, --comment, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.

Zfinix/aster · 75 tokens

rtl-review

Audit RTL code for lint violations, synthesis hazards, coding-style compliance, and readability. Use when the user says "review this Verilog", "check my RTL", "lint this module", "is this code synthesizable", or shares an HDL file and asks for feedback before simulation or tape-in.

vibeic/vibe-ic · 63 tokens