claude-piv-skeleton: Command for Claude Code

.claude/commands/validation/suggest-improvement.md

suggest-improvement is a command for Claude Code from plipowczan/claude-piv-skeleton. It costs 11 tokens per session (971 once invoked), scanned A, original, MIT.

A command that creates a structured suggestion for improving a project rule, validation check, or coding skill, based on findings from code reviews.

In plain words
What is it for?
Use it to propose new rules, stronger validation commands, or improved skills, with context about the issue, its frequency, and its impact.
Why use it?
It turns repeated review problems into a proposed change instead of leaving the same issue to be found again and again.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

This is plipowczan/claude-piv-skeleton's own configuration. It tells Claude Code how to work on claude-piv-skeleton 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 claude-piv-skeleton configures →

Part of the piv-speckit plugin — 6 skills, 16 commands shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to plipowczan/claude-piv-skeleton. 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/plipowczan/claude-piv-skeleton/main/.claude/commands/validation/suggest-improvement.md
Clone the repo
git clone --depth 1 https://github.com/plipowczan/claude-piv-skeleton

Made for: Claude Code.

Or install piv-speckit, the plugin that ships this one along with the rest of its 6 skills, 16 commands.

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 suggest-improvement

README.md
[![agentmods](https://agentmods.dev/badge/commands/plipowczan/claude-piv-skeleton/suggest-improvement/github.svg)](https://agentmods.dev/commands/plipowczan/claude-piv-skeleton/suggest-improvement)
Your own site
<a href="https://agentmods.dev/commands/plipowczan/claude-piv-skeleton/suggest-improvement"><img src="https://agentmods.dev/badge/commands/plipowczan/claude-piv-skeleton/suggest-improvement/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 suggest-improvement

Your own site · 80×15
<a href="https://agentmods.dev/commands/plipowczan/claude-piv-skeleton/suggest-improvement"><img src="https://agentmods.dev/badge/commands/plipowczan/claude-piv-skeleton/suggest-improvement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 971 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.00011 $0.00971
Opus 5 $0.00005 $0.00485
Sonnet 5 $0.00002 $0.00194
Haiku 4.5 $0.00001 $0.00097

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

Security

Grade A, and why

suggest-improvement 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 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.

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.

.claude/commands/validation/suggest-improvement.md · 167 lines

How it starts

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

Suggest Improvement: Generate Rule/Validation/Skill Enhancement

Purpose

Create a structured improvement suggestion artifact that proposes changes to:

  • Rules (.claude/rules/*.md) - Add patterns, anti-patterns, examples
  • Validation (.claude/commands/validation/*.md) - Add checks
  • Skills (.claude/skills/*.md) - Add enforcement behaviors

Prerequisites

  • Learning insights exist (run /piv-speckit:learn first)
  • Improvement is based on real data from code reviews

Arguments

Argument Description Example
type Type of improvement (rule, validation, skill) rule
title Brief title of the improvement "Add N+1 query detection"

Process

Step 1: Gather Context

Read learning insights from .claude/agents/learning/insights/ to understand:

  • What issue/pattern prompted this suggestion
  • How many times it occurred
  • What the impact was

Step 2: Identify Target File

Based on type:

  • rule: Determine which rule file (security, testing, general, etc.)
  • validation: Determine which validation command to enhance
  • skill: Determine which skill to enhance or create

Step 3: Propose Change

Determine:

  • What content to add
  • Where to add it (section, line)
  • How it will prevent the issue

Step 4: Create Improvement Artifact

Create at: .claude/agents/learning/suggestions/{suggestion-id}.md

Generate unique suggestion-id: {type}-{short-title}-{timestamp}

Example: rule-n1-query-detection-20250115

Structure:

# Improvement Suggestion: {Title}

**ID:** {suggestion-id}
**Date:** {timestamp}
**Type:** {rule-update | validation-addition | skill-enhancement}
**Priority:** {critical | high | medium | low}
**Status:** pending

## Problem

{Description of the recurring issue or gap}

## Evidence

Based on learning analysis:
- **Found in:** {N} code reviews
- **Last occurrence:** {date}
- **Source reviews:**
  - `.claude/agents/reviews/{review1}.md`
  - `.claude/agents/reviews/{review2}.md`
- **Impact:** {description of impact}

## Proposed Change

### Target File
`{path to file to update}`

### Section
{Which section to add to}

### Proposed Content

```{language}
{The actual content to add}

Rationale

{Why this change will prevent the issue}

Validation

After applying this change:

  1. {How to verify it works}
  2. {Expected behavior}

Risks

  • {Potential downside 1}
  • {Potential downside 2}

Approval

  • Reviewed by human
  • Approved for implementation
  • Applied to codebase

Application Instructions

To apply this improvement:

  1. Review the proposed change above
  2. If approved, update {target file} with the proposed content
  3. Run validation to ensure no regressions
  4. Mark as applied and move to .claude/agents/learning/applied/

Read the full file on GitHub · 167 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 · 167 lines · 11 tokens per session scan A b73124334f6c

Subscribe to this mod's changes

suggest-improvement is a command published in the GitHub repository plipowczan/claude-piv-skeleton (4 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 971 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-08-31.