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.
npx skills add causify-ai/helpers --skill readme_file.creategit clone --depth 1 https://github.com/causify-ai/helpersWrote 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.
[](https://agentmods.dev/skills/causify-ai/helpers/readme_file.create)<a href="https://agentmods.dev/skills/causify-ai/helpers/readme_file.create"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/readme_file.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.
<a href="https://agentmods.dev/skills/causify-ai/helpers/readme_file.create"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/readme_file.create.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00011 | $0.00457 |
| Opus 5.5 | $0.00004 | $0.00183 |
| Sonnet 5.5 | $0.00002 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
readme_file.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 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.
This is a copy
86% identical to readme_file.create — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Goal
- You are an expert technical writer specializing in software documentation
- Given a file path
<FILE>(typically an executable), write or update<FILE>.README.mdin the same directory - Follow the conventions in
.claude/skills/readme_file.rules.md - Follow the template
.claude/templates/readme_file.template.md
Workflow
Read the File
- Read
<FILE>and identify:- The entry point and the argument parser (flags, types, defaults)
- The inputs, outputs, and side effects (files, exit codes, logging)
- The key functions and the data flow
Check the Existing README
- If
<FILE>.README.mdexists, read it and plan what to update - If it does not exist, plan content from scratch
Write the README
- Write
<FILE>.README.mdwith the sections from.claude/skills/readme_file.rules.md:- Summary
- Examples
- Configuration & Inputs
- Output & Side Effects
- Software Architecture
- For the Software Architecture section, reuse the steps of
.claude/skills/readme_file.write_architecture/SKILL.md - Follow all formatting rules from
.claude/skills/readme_file.rules.md:- Examples ordered from simple to complex
- Commands as bullet + fenced block with the
>prefix - Argument reference as a table
Point to the README from the File
- Make sure the docstring of
<FILE>points to<FILE>.README.md, e.g.,For a description of this file, see the file <FILE>.README.md
Verification
-
<FILE>.README.mdexists in the same directory as<FILE> - Every required section from
.claude/skills/readme_file.rules.mdis present - Every argument of the parser appears in the arguments table
- The docstring of
<FILE>points to<FILE>.README.md
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.
- 4d ago First seen · 58 lines · 11 tokens per session scan A 975c81019700
readme_file.create is a skill published in the GitHub repository causify-ai/helpers (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 11 tokens to every session and 457 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to readme_file.create, differing in 24 lines, and is treated as a copy.
readme_file.create compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| readme_file.createcausify-ai/helpers | Skill | 0 | 5d ago | Apache-2.0 | A | 11 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |