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 sorah/config --skill readmegit clone --depth 1 https://github.com/sorah/configWrote 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/sorah/config/readme)<a href="https://agentmods.dev/skills/sorah/config/readme"><img src="https://agentmods.dev/badge/skills/sorah/config/readme/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/sorah/config/readme"><img src="https://agentmods.dev/badge/skills/sorah/config/readme.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.00103 | $0.02988 |
| Opus 5.5 | $0.00041 | $0.01195 |
| Sonnet 5.5 | $0.00021 | $0.00598 |
| Haiku 4.5 | $0.00010 | $0.00299 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README
Conventions for composing READMEs for open source libraries, CLI tools, and services. Derived from sorah's own projects and from the top-downloaded crates.io and rubygems.org projects. Project-specific conventions and an existing README's established style always take priority.
A README has one job: let a stranger decide within one screen whether the project solves their problem, then get them to a working first use. Everything else is optional and must earn its place.
Workflow
- Gather facts from the repository before writing. Never invent them.
- Name, package name, and registry (
*.gemspec,Cargo.toml,package.json,go.mod) - Actual install channels: published gem/crate, Homebrew tap, AUR, container image, GitHub release binaries (check CI release workflows)
- Minimum language/runtime version (
required_ruby_version,rust-version,engines) - CLI help output (
--help) and real config samples in the repo (config.sample.yml,contrib/,examples/) LICENSE*files and copyright holder;SECURITY.md,CONTRIBUTING.md,docs/- Upstream projects it wraps, replaces, or was inspired by
- Name, package name, and registry (
- Classify the project (see Project Shapes) to pick a skeleton and length.
- Write the opening (title, tagline, first paragraph) first. If it cannot be written in two sentences, the project's positioning is unclear. Ask the user rather than pad.
- Write the smallest working example, then fill remaining sections.
- Verify every command, path, flag, and link against the repository. Run the example when feasible.
- Review against the Checklist.
When improving an existing README, preserve its voice, heading style, and structure unless asked for a rewrite. Fix inaccuracies and stale content first, then add missing essentials.
Project Shapes
| Shape | Examples | Length | Notes |
|---|---|---|---|
| Foundational library | libc, itoa, cfg-if | Very short | Purpose sentence, dependency snippet, one example, docs link, MSRV, license |
| Focused library | thiserror, anyhow, webmock, hocho | Short–medium | Example-driven; README may be the manual |
| Framework / large library | tokio, sidekiq, faraday | Medium, docs elsewhere | README is a hub: pitch, minimal example, links to guides/API docs |
| CLI tool | ripgrep, fd, mairu, envchain | Medium–long | Install matrix, quick usage, config, comparisons |
| Service / daemon | himari, ecamo, needroleshere | Medium–long | How it works, setup, configuration, security model, caveats |
What ships with it
6 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.
- yesterday First seen · 188 lines · 103 tokens per session scan A f0ade18ba1e3
readme is a skill published in the GitHub repository sorah/config (31 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 2,988 once invoked, about $0.0004 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-10-17.
Other skills, from other repositories
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…
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.