What is readme_dir.create?

A README writer for a directory that documents its folders, files, and executable programs. README.md is the standard Markdown guide people read first when exploring a code directory.

Use it to create or update project documentation, including a file map, executable descriptions, test instructions, and a review roadmap.

It turns a directory's contents into a consistent guide, so new contributors can understand what is there and how to run its programs and tests.

readme_dir.create — Skill for Claude Code by gpsaggese/helpers

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.

Any agent

npx skills add gpsaggese/helpers --skill readme_dir.create

Clone the repo

git clone --depth 1 https://github.com/gpsaggese/helpers

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/gpsaggese/helpers/readme_dir.create/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/readme_dir.create)

Your own site

<a href="https://agentmods.dev/skills/gpsaggese/helpers/readme_dir.create"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/readme_dir.create/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gpsaggese/helpers/readme_dir.create"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/readme_dir.create.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,329 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.00016	$0.02329
Opus 5.5	$0.00006	$0.00932
Sonnet 5.5	$0.00003	$0.00466
Haiku 4.5	$0.00002	$0.00233

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

Security

Grade A, and why

readme_dir.create 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 yesterday.

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/readme_dir.create/SKILL.md · 197 lines

How it starts

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

Goal

You are an expert technical writer specializing in software documentation.
Given a dir <DIR>, write its README.md following .claude/skills/readme_dir.rules.md and the template .claude/templates/readme_dir.template.md

Say in the README how it was generated, with the line

- Generated by `.claude/skills/readme_dir.create/SKILL.md`

End the README with the section # Review roadmap: the map of the dir, how to run the tests, the reading speeds, and the table of files with the time to read each one
- The skill .claude/skills/review.create_code_tour/SKILL.md reads this section to write the checklist that guides the review of the dir

Workflow

Examine the Directory

List all subdirectories, files (Python/Markdown), and executables

Write the README

Put the Generated by ... bullet from the Goal right after the title, before the Summary bullets
Structure the README with the sections from .claude/skills/readme_dir.rules.md:
- Summary, as bold-labeled bullets (Goal, Input, Output, Users)
- Structure of the Dir
- Description of Files
- Description of Executables (if applicable)
- Output Dir (if the executables write a tree of files in one dir), as a ## section of the executables, before the first executable
- Description of Workflows (if applicable)
- Description of Architecture (if applicable)
- Review roadmap, as the last section, see "Write the Review Roadmap"
Follow all formatting rules from .claude/skills/readme_dir.rules.md:
- Description limits (e.g., <20 words for subdirs, 1-line for files)
- Command formatting with > prefix and proper code blocks
- Example ordering (simple to complex)
- Table format for command references
- Bullets only, no prose paragraphs, including the intro of each section
- Many outputs as one sub-bullet per file or per group of files

Check the Commands

Check each example command against the current CLI of its executable (e.g., with --help)
Remove the args that the tool dropped, and rename the args that the tool renamed
Check the commands in the workflows too

Read the full file on GitHub · 197 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.

yesterday First seen · 197 lines · 16 tokens per session scan A bb846aa7fa78

Subscribe to this mod's changes

readme_dir.create is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 2,329 once invoked, about $0.0001 per session on Opus 5.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-11-06.

Documents Writing and docs

readme_dir.create next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
readme_dir.creategpsaggese/helpers	Skill	158	today	Apache-2.0	A	16	Claude Code
orbit-notionnexu-io/open-design	Skill	106k	today	Apache-2.0	A	117	Claude Code, Codex
instrument-data-to-allotropeanthropics/knowledge-work-plugins	Skill	35k	today	Apache-2.0	A	123	Claude Code
apify-youtube-transcript-scrapersickn33/agentic-awesome-skills	Skill	49k	yesterday	MIT	A	48	Claude Code
legal-holdanthropics/claude-for-legal	Skill	9.9k	today	Apache-2.0	A	68	Claude Code
report-to-pdfasgeirtj/system_prompts_leaks	Skill	71k	today	CC0-1.0	A	17	Claude Code, Codex
artifact-template-minimal-letterheadasgeirtj/system_prompts_leaks	Skill	71k	today	CC0-1.0	A	54	Claude Code, Codex