revise-structure

revise-structure is a skill for Claude Code from OC-NeuralSense/reader-first-writing-skills. It costs 185 tokens per session (2,318 once invoked), scanned A, original, Apache-2.0.

A skill for reorganising a document’s structure while keeping its meaning unchanged. It repairs how points are grouped, ordered, and summarised after a specific structural problem has been identified.

In plain words
What is it for?
Use it to regroup claims, reorder sections, and revise summaries according to an existing structure plan and defect report.
Why use it?
It fixes arguments or documents whose ideas are in the wrong groups or sequence. It focuses on arrangement rather than rewriting the wording or adding new claims.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the reader-first-writing plugin — 12 skills, 3 agents shipped together

Good fit Use it to regroup claims, reorder sections, and revise summaries according to an existing structure plan and defect report.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add OC-NeuralSense/reader-first-writing-skills
Claude Code
/plugin install reader-first-writing

Made for: Claude Code.

Or install reader-first-writing, the plugin that ships this one along with the rest of its 12 skills, 3 agents.

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 revise-structure

README.md
[![agentmods](https://agentmods.dev/badge/skills/oc-neuralsense/reader-first-writing-skills/revise-structure/github.svg)](https://agentmods.dev/skills/oc-neuralsense/reader-first-writing-skills/revise-structure)
Your own site
<a href="https://agentmods.dev/skills/oc-neuralsense/reader-first-writing-skills/revise-structure"><img src="https://agentmods.dev/badge/skills/oc-neuralsense/reader-first-writing-skills/revise-structure/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 revise-structure

Your own site · 80×15
<a href="https://agentmods.dev/skills/oc-neuralsense/reader-first-writing-skills/revise-structure"><img src="https://agentmods.dev/badge/skills/oc-neuralsense/reader-first-writing-skills/revise-structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 185 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,318 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.00185 $0.02318
Opus 5 $0.00093 $0.01159
Sonnet 5 $0.00037 $0.00464
Haiku 4.5 $0.00018 $0.00232

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

Security

Grade A, and why

revise-structure 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 11d 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/revise-structure/SKILL.md · 200 lines

How it starts

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

revise-structure

Purpose

Repair the architecture of a document -- its grouping, ordering, summaries, and membership -- so a named structural defect stops reproducing, while holding the meaning constant. This skill rearranges what sits where and what stands over what; it does not polish sentences.

When to use

  • A structural defect is known (from diagnose-draft or test-argument) and the user wants it fixed.
  • "Fix the structure", "re-group / re-order / re-summarize", "the arrangement is wrong".

When NOT to use

  • The problem is sentence flow, clarity, length, or thinness -> revise-prose.
  • The user only wants to know whether it is broken -> diagnose-draft / test-argument.

Inputs

  • draft_or_outline (the material to restructure).
  • argument-blueprint contract (the validated structure object and claim set).
  • defect-report contract (the located structural findings driving the repair).

Workflow

  1. Read the defect-report; take the structural findings and their locations as the work list. Read the blueprint to fix the canonical claim set before any change.
  2. Apply only structural operations:
    • re-group -- move a claim under the parent it actually belongs to;
    • re-order -- sequence a group by one consistent principle (time, part structure, or degree);
    • re-summarize -- rewrite a parent so it honestly summarizes its children (no empty toppers, no overreach);
    • cut -- remove a claim that earns no place, recording it on the drop list.
  3. After each change, confirm the named defect no longer reproduces.
  4. Run the fidelity check: the pre/post claim set must be identical -- same propositions, numbers, dates, names, negations, modality, conditions, exceptions, and qualifiers. List every claim moved, merged, re-summarized, or cut.
  5. Re-run the soundness test (outline-validator): every parent-child link still genuinely follows; no restructuring created or hid a non-sequitur.
  6. Emit the revised structure and a change-report.

Read the full file on GitHub · 200 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. 11d ago First seen · 200 lines · 185 tokens per session scan A bb1e4db1a127

Subscribe to this mod's changes

revise-structure is a skill published in the GitHub repository OC-NeuralSense/reader-first-writing-skills (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 185 tokens to every session and 2,318 once invoked, about $0.0009 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.