readme-restructure

readme-restructure is a command for Claude Code from Hulupeep/Specflow. It costs 0 tokens per session (715 once invoked), scanned A, original, MIT.

A command that rewrites a README using an approved audit plan, moving detailed material into linked documentation where appropriate.

In plain words
What is it for?
Use it after running and approving readme-audit, when you want to reorganize the README, create documentation files, and add links between them.
Why use it?
It turns a long or unclear README into a shorter path from evaluation to action while preserving useful existing information in separate documents.

Command for Claude Code

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.

agentmods
npx agentmods add commands/hulupeep/specflow/readme-restructure
Clone the repo
git clone --depth 1 https://github.com/Hulupeep/Specflow

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 readme-restructure

README.md
[![agentmods](https://agentmods.dev/badge/commands/hulupeep/specflow/readme-restructure.svg)](https://agentmods.dev/commands/hulupeep/specflow/readme-restructure)
Your own site
<a href="https://agentmods.dev/commands/hulupeep/specflow/readme-restructure"><img src="https://agentmods.dev/badge/commands/hulupeep/specflow/readme-restructure.svg" alt="Measured on agentmods" 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 715 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00715
Opus 5 $0.00000 $0.00358
Sonnet 5 $0.00000 $0.00143
Haiku 4.5 $0.00000 $0.00072

Measured 4d ago against content hash 99a737d969cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

readme-restructure 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 4d 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/readme-restructure.md · 114 lines

How it starts

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

README Restructure

Execute a /readme-audit blueprint. Rewrites the README to the evaluator → conversion → links structure and creates linked docs by extracting and reorganising existing content.

This skill modifies files. Always run /readme-audit first and confirm the blueprint before running this.

Before Starting

Confirm:

  1. /readme-audit has been run and produced a blueprint (or paste one)
  2. Which promoted sections map to existing docs vs need to be created
  3. README path
  4. Output directory for new docs (default: docs/)

Process

Step 1: Confirm Before Touching Files

Print a summary of planned changes and wait for user confirmation:

PLANNED CHANGES:
  README.md: ~[N] lines → ~[N] lines

  Creating [N] new docs:
    docs/[name].md — from [source sections]
    ...

  Sections being cut: [list]
  Sections being merged into: [list]

  Confirm? (yes to proceed)

Step 2: Create the Extracted Docs

For each doc in the blueprint:

  1. Read all source sections from the original README
  2. Write a short intro (1–2 sentences) so the doc works standalone
  3. Include all relevant content, removing internal duplication
  4. Add a back-link to the README at the bottom
  5. Write to the output directory using kebab-case filenames

Do NOT copy-paste sections raw. Synthesise so each doc reads coherently as a standalone document.

Step 3: Rewrite the README

Target structure:

# [Product Name]
[tagline]

[Evaluator content — max 3 sections, max 10 lines each]

---

## Get Started

[One install command or one clear action — the conversion moment]

---

## What do you need?

| I want to... | Go here |
|---|---|
| [path] | [link] |
...

---
[License]

Rules:

  • Evaluator section: max 3 sections, max 10 lines each
  • Conversion moment: single command or single clear action
  • Links table covers ALL reader paths — no orphaned content
  • Nothing appears in both the README and a linked doc
  • No section requires prior product knowledge to understand

Read the full file on GitHub · 114 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. 4d ago First seen · 114 lines · 0 tokens per session scan A 99a737d969cb

Subscribe to this mod's changes

readme-restructure is a command published in the GitHub repository Hulupeep/Specflow (24 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 715 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-08-30.