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 instructions/ryanlyn/readwise-skill/claude-mdgit clone --depth 1 https://github.com/ryanlyn/readwise-skillWhat 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.00635 | $0.00635 |
| Opus 5 | $0.00318 | $0.00318 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
readwise-skill CLAUDE.md 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 2d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Readwise Skill
Claude Code marketplace providing the readwise plugin for automating Readwise workflows.
Scope
- Python development happens in
plugins/readwise/. - Prefer repo-local CLI paths over any installed plugin cache.
Installation
In Claude Code:
/plugin marketplace add ryanlyn/readwise-skill
/plugin install readwise@readwise-skill
Then set READWISE_TOKEN (Readwise access token) as an environment variable or Claude Code secret.
Development
Plugin source lives in plugins/readwise/.
cd plugins/readwise
uv sync --extra dev
uv run pytest -v
uv run python -m compileall skills/readwise skills/readwise-reader readwise_common
uv run ruff check --fix .
uv run ruff format .
- Normal
uv run pytestruns the full test suite and enforces 100% coverage forreadwise_common,skills/readwise/scripts, andskills/readwise-reader/scripts. pytestalready starts the in-memory stub server fromtests/conftest.py, so normal test runs do not need a separate server process.
Local CLI workflows
Use local files when working in this repo:
cd plugins/readwise
uv run python skills/readwise/scripts/readwise_client.py --help
uv run python skills/readwise-reader/scripts/reader_client.py --help
- Both CLIs support global
--dry-run,--raw, and--tokenoptions. - Global options can appear anywhere in the command.
Zip Distribution
Build standalone skill zips for agent harnesses such as Codex and OpenClaw:
uv run python scripts/build_skill_zips.py --clean
Run packaging verification:
bash scripts/verify_skill_zips.sh
scripts/verify_skill_zips.shbuilds the zip artifacts, unpacks them, runscompileall, and smoke-tests both CLIs with--help.- Artifacts are written to
dist/zips/asreadwise-<version>.zipandreadwise-reader-<version>.zip. - CI publishes these zip artifacts on pushes to
mainafter verification passes.
Development Tips
- Shared code lives in
plugins/readwise/readwise_common/for auth, HTTP retries, models, formatting utilities, and helpers. - Models in
plugins/readwise/readwise_common/models.pydefine Pydantic payloads for API requests and responses. Update these when adding new fields. - CLI help text should include valid values for options like
books|articles|tweets|podcasts. Agents read--helpwhen unsure. SKILL.mdis what agents see, so keep CLI examples and valid option values in sync with the actual code.
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.
- 2d ago First seen · 81 lines · 635 tokens per session scan A 6fd223efa85a
readwise-skill CLAUDE.md is an instructions file published in the GitHub repository ryanlyn/readwise-skill (24 stars, last pushed 5mo ago), licensed MIT. It adds 635 tokens to every session, about $0.0032 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.