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 agentmods add skills/codebygarv/ai-skills/readme-buildernpx skills add codebygarv/Ai-skills --skill readme-buildergit clone --depth 1 https://github.com/codebygarv/Ai-skillsWrote 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/codebygarv/ai-skills/readme-builder)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/readme-builder"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/readme-builder.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00483 |
| Opus 5 | $0.00019 | $0.00242 |
| Sonnet 5 | $0.00008 | $0.00097 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
readme-builder 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Produce a professional, complete README for a GitHub project that lets a newcomer understand what the project is, install it, and start using it — without needing to read the source first.
When to Use
- A repository has no README, or one that's thin/outdated.
- Preparing a project for public release or wider internal sharing.
- The user asks for "a README" for a project.
What to Analyze / Do
- Determine what the project actually is — from the codebase, package manifest, or the user's description: language/framework, what it does, its entry points.
- Cover the standard sections, adapted to project type:
- Title + one-line description
- What it does / why it exists (a short "why would I use this" paragraph)
- Installation (exact commands, from a clean environment)
- Usage (a minimal working example)
- Configuration (if applicable — env vars, config file)
- Project structure (for non-trivial repos, a brief tree/overview)
- Contributing (link out to CONTRIBUTING.md if one exists, or a short inline section)
- License
- Verify commands are accurate — don't invent install/run commands; check the actual package manifest/scripts/Makefile for what's real.
- Match the project's actual maturity — a weekend script doesn't need a "Roadmap" and "Governance" section; a serious open-source library might.
Output Format
- Full README.md in Markdown, badges only if genuinely applicable (CI status, npm version) and not invented.
- Code blocks with correct language tags for every command/example.
- Concise — a README that's skimmable in under a minute for the essentials (what/install/usage), with more detail below for those who want it.
Avoid
- Inventing installation commands, scripts, or features that don't exist in the actual project.
- Copy-pasting a generic README template without adapting section relevance to the actual project.
- Writing a README so long that the essential "what is this and how do I run it" gets buried.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 42 lines · 38 tokens per session scan A 423eaaa2c944
readme-builder is a skill published in the GitHub repository codebygarv/Ai-skills (24 stars, last pushed 14d ago), licensed MIT. It adds 38 tokens to every session and 483 once invoked, about $0.0002 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.
Other skills, from other repositories
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis for Redis/Valkey, Bun.Archive for tarballs, Bun.Image image processing, Bun.WebView…
bun-cli
Bun CLI reference for package management, script running, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace catalogs, isolated installs and the global…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…