experiments: Command for Claude Code

.cursor/commands/improve-code-quality.md

improve-code-quality is a command for Claude Code, Cursor from reliverse/experiments. It costs 0 tokens per session (2,998 once invoked), scanned A, original, MIT.

A command for systematically improving the quality of package-library code while preserving its behaviour. It focuses on clearer code, less duplication, better separation into modules, and easier maintenance.

In plain words
What is it for?
Use it to review and refactor the listed packages, prioritising packages that have not been improved recently.
Why use it?
It gives refactoring work a defined order and goal instead of relying on ad hoc cleanup. This helps improve difficult-to-maintain packages without intentionally changing what they do.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md).

This is reliverse/experiments's own configuration. It tells Claude Code and Cursor how to work on experiments itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything experiments configures →

Reuse

Borrowing it

Nothing to install: this file belongs to reliverse/experiments. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/reliverse/experiments/main/.cursor/commands/improve-code-quality.md
Clone the repo
git clone --depth 1 https://github.com/reliverse/experiments

Made for: Claude Code, Cursor.

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 improve-code-quality

README.md
[![agentmods](https://agentmods.dev/badge/commands/reliverse/experiments/improve-code-quality/github.svg)](https://agentmods.dev/commands/reliverse/experiments/improve-code-quality)
Your own site
<a href="https://agentmods.dev/commands/reliverse/experiments/improve-code-quality"><img src="https://agentmods.dev/badge/commands/reliverse/experiments/improve-code-quality/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 improve-code-quality

Your own site · 80×15
<a href="https://agentmods.dev/commands/reliverse/experiments/improve-code-quality"><img src="https://agentmods.dev/badge/commands/reliverse/experiments/improve-code-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,998 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.00000 $0.02998
Opus 5.5 $0.00000 $0.01199
Sonnet 5.5 $0.00000 $0.00600
Haiku 4.5 $0.00000 $0.00300

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

Security

Grade A, and why

improve-code-quality 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.

.cursor/commands/improve-code-quality.md · 313 lines

How it starts

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

Improve code quality (clarity, DRY, modularity)

Purpose

This command guides the AI to improve a package library's code quality using a systematic refactoring approach. The goal is to enhance code clarity, reduce duplication (DRY), improve modularity, and maintainability while ensuring functionality remains intact.

Packages to Improve

The following packages should be improved in priority order (packages with older lastImproved timestamps should be prioritized):

# Package Last Improved Status Notes
0 @reliverse/dler - - -
1 @reliverse/build - - -
2 @reliverse/bump - - -
3 @reliverse/config - - -
4 @reliverse/datetime - - -
5 @reliverse/helpers - - -
6 @reliverse/mapkit - - -
7 @reliverse/matcha - - -
8 @reliverse/pathkit - - -
9 @reliverse/publish - - -
10 @reliverse/relico - - -
11 @reliverse/relifso - - -
12 @reliverse/relinka - - -
13 rempts - - -
14 @reliverse/tsconfig - - -
15 @reliverse/typerso - - -

Metadata Fields:

  • Last Improved: Timestamp (CET timezone) when code quality improvements were last completed (format: YYYY-MM-DD HH:mm:ss)
  • Status: Current improvement status (pending, in-progress, completed, skipped)
    • in-progress: ⚠️ CRITICAL: If a package has status in-progress, it means another AI agent is currently working on it. DO NOT select or work on packages with this status. Skip them and move to the next available package.
  • Notes: Any relevant information about the package or improvement results

Read the full file on GitHub · 313 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. 1mo ago First seen · 313 lines · 0 tokens per session scan A bb8bbc38e299

Subscribe to this mod's changes

improve-code-quality is a command published in the GitHub repository reliverse/experiments (117 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,998 tokens. 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-01.