What is update-readme?

A workflow for updating a project's README so its feature list and technology list match the code and dependency version catalog.

Use it to compare feature folders, recent commits, and dependency versions with the README, then update only outdated sections.

It prevents documentation from becoming inaccurate as features, libraries, and versions change.

How CinqueIzumi/Softcover configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to CinqueIzumi/Softcover. 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/CinqueIzumi/Softcover/main/.claude/skills/update-readme/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/CinqueIzumi/Softcover

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cinqueizumi/softcover/update-readme.svg)](https://agentmods.dev/skills/cinqueizumi/softcover/update-readme)

Your own site

<a href="https://agentmods.dev/skills/cinqueizumi/softcover/update-readme"><img src="https://agentmods.dev/badge/skills/cinqueizumi/softcover/update-readme.svg" alt="Measured on agentmods" height="20"></a>

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 409 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.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.00409
Opus 5	$0.00014	$0.00204
Sonnet 5	$0.00006	$0.00082
Haiku 4.5	$0.00003	$0.00041

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

Security

Grade A, and why

update-readme 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 8d 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/skills/update-readme/SKILL.md · 24 lines

What it actually says

Keep README.md in sync with what the app actually ships — both the Features section (against the feature modules) and the Tech Stack section (against the version catalog) — so the README never goes stale. README only — do not commit.

Steps:

Use the Bash tool to list the directories under feature/ — this is the source of truth for what features exist.
Read the Features section of README.md (grouped by user-facing area: Library, Reading, Explore, Book Details, Profile, Settings). Use the Bash tool to run git log since the last release tag/version to see what changed recently.
Compare: find features present in the code (or recent commits) that are missing or described inaccurately in the README.
Use the Edit tool to update the Features section. Keep the existing editorial grouping and tone, and add or adjust only what changed — do not rewrite sections that are still accurate. Preserve the heading structure and the Table of Contents.
Read gradle/libs.versions.toml — the source of truth for libraries and their versions. Compare it against the Tech Stack tables in the README. Use the Edit tool to:
- Correct any version string that has drifted.
- Add a row for any library that is now in the catalog (and meaningfully part of the stack) but missing from the tables, placing it in the right table (Core, Data & Networking, App Architecture, Testing) and matching the existing row format.
- Remove rows for libraries that have been dropped from the catalog. Keep the tables' existing structure and column layout.
Report a short summary of what changed (features + tech stack).

Do not create a commit. Do not modify anything outside README.md.

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.

8d ago First seen · 24 lines · 28 tokens per session scan A 6a83c84e82ab

Subscribe to this mod's changes

update-readme is a skill published in the GitHub repository CinqueIzumi/Softcover (11 stars, last pushed 7d ago), licensed MIT. It adds 28 tokens to every session and 409 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-30.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

Softcover: Skill for Claude Code