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 vosslab/vosslab-skills --skill readme-docsgit clone --depth 1 https://github.com/vosslab/vosslab-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/vosslab/vosslab-skills/readme-docs)<a href="https://agentmods.dev/skills/vosslab/vosslab-skills/readme-docs"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/readme-docs.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.1 | $0.00056 | $0.02875 |
| Opus 5 | $0.00028 | $0.01437 |
| Sonnet 5 | $0.00011 | $0.00575 |
| Haiku 4.5 | $0.00006 | $0.00287 |
Grade A, and why
readme-docs 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 6d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README landing page
Goal
Make README.md a useful front door for a first-time visitor. Explain what the
project does, why it matters, and how to try it. Give readers enough context and
proof to decide whether the project fits their needs, then route them to deeper
documentation.
Optimize for comprehension, successful onboarding, and a memorable project identity. Give newcomers enough context, evidence, and guidance to understand the work before the documentation links.
This skill is the sole owner of README.md. Other docs skills own their files under
docs/; this skill summarizes the most important user-facing information and links
to those authoritative details.
Resource routing
The workflow below contains the required process. Load a supporting resource when its decision applies:
- Use assets/README_TEMPLATE.md when the README is missing, very thin, or needs a structural rewrite.
- Read references/readme_best_practices.md when choosing among unfamiliar project types or resolving a structure or content question.
- Read references/landing_page_ideas.md when the page needs a stronger signature promise, proof artifact, or project-specific treatment.
- Apply references/review_checklist.md for a broad refresh or a final landing-page audit.
- Apply references/scoring_rubric.md for a broad refresh, an explicit scoring request, or a before-and-after quality comparison.
Adapt the template to repository evidence and resolve every placeholder before delivery.
Landing-page standard
Answer these questions in the order a newcomer is likely to ask them:
- What is this project?
- Who is it for, and what problem does it solve?
- Why would someone choose or use it?
- What does it look like or produce?
- How can someone get a meaningful first result?
- Where can they learn more?
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.
- 6d ago First seen · 277 lines · 56 tokens per session scan A 6abaed2fee59
readme-docs is a skill published in the GitHub repository vosslab/vosslab-skills (2 stars, last pushed 11d ago), licensed MIT. It adds 56 tokens to every session and 2,875 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…