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 Abilityai/abilities --skill read-docsgit clone --depth 1 https://github.com/Abilityai/abilitiesWrote 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/abilityai/abilities/read-docs)<a href="https://agentmods.dev/skills/abilityai/abilities/read-docs"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/read-docs/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/abilityai/abilities/read-docs"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/read-docs.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.00014 | $0.00712 |
| Opus 5.5 | $0.00006 | $0.00285 |
| Sonnet 5.5 | $0.00003 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
read-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 1mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read Project Documentation
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.read-docs vX.Y — recent: <summary>. Then proceed.
Load all project documentation into context for this session.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| Requirements | docs/memory/requirements.md |
✅ | Feature requirements | |
| Architecture | docs/memory/architecture.md |
✅ | System design | |
| Feature Flows | docs/memory/feature-flows.md |
✅ | Flow index | |
| GitHub Issues | GitHub repo | ✅ | P0/P1 issues | |
| Changelog | docs/memory/changelog.md |
✅ | Recent changes |
Process
Step 1: Read Core Documentation
Read these files in full (no summaries until all are loaded):
docs/memory/requirements.md- Feature requirements (SINGLE SOURCE OF TRUTH)docs/memory/architecture.md- Current system designdocs/memory/feature-flows.md- Feature flow index
Step 2: Query GitHub Roadmap
Query P0 and P1 issues from GitHub Issues:
# P0 issues (urgent, do immediately)
gh issue list --label "priority-p0" --state open --json number,title,labels
# P1 issues (critical path)
gh issue list --label "priority-p1" --state open --json number,title,labels
Step 3: Read Recent Changelog
Read changelog using Bash (file may be large, only need recent entries):
head -150 docs/memory/changelog.md
Note: CLAUDE.md is loaded automatically at session start - no need to read it again.
Step 4: Understand Project State
- What features are implemented?
- What's currently in progress?
- What are the current priorities from GitHub Issues?
Step 5: Report Completion
Documentation loaded. Ready to work on {{PROJECT_NAME}}.
P0: [P0 issues or "None"]
P1: [P1 issues]
Recent: [most recent changelog entry]
When to Use
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.
- 1mo ago First seen · 96 lines · 14 tokens per session scan A 46da9b15d11f
read-docs is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 712 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-09-07.
Other skills, from other repositories
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
gsd-mempalace-capture
File a phase artifact into MemPalace; mirror decision facts into its temporal KG.
md-hive-sync
Munder Difflin hive sync — runs the start-of-task hive protocol steps: reads memory.md, checks inbox/ for new messages, and reminds you to record durable facts in memory.md and write coordination files before ending. Use when asked to "sync with the hive", "check my inbox", "hive status", or "hive sync". Proactively…
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
rem-page-org
What an organisation's page in the notebook is made of — the fixed sections, when a company earns a page at all instead of staying a field on a person's, and the rules that keep it from becoming a second copy of everyone who works there. Composed into every stage that writes one.