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/lilmgenius/paperthin/readchknpx skills add LilMGenius/paperthin --skill readchkgit clone --depth 1 https://github.com/LilMGenius/paperthinWrote 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/lilmgenius/paperthin/readchk)<a href="https://agentmods.dev/skills/lilmgenius/paperthin/readchk"><img src="https://agentmods.dev/badge/skills/lilmgenius/paperthin/readchk.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.00088 | $0.00557 |
| Opus 5 | $0.00044 | $0.00279 |
| Sonnet 5 | $0.00018 | $0.00111 |
| Haiku 4.5 | $0.00009 | $0.00056 |
Grade A, and why
readchk 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check the read before acting: did you understand the instruction correctly enough to spend the work?
Goal
readchk catches misread instructions before they become coherent work against the wrong target. It verifies a claim about the requester's intent against available context: the current message, session history, project memory, files on disk, and established conventions.
This is not factchk: the question is what was meant, not whether a world claim is true.
Workflow
- Recognize the signal: a long or multi-part instruction, ambiguous scope or referents, deliberately flexible wording, or stakes high enough that a wrong guess would cost real work.
- Restate the instruction internally in different words. Do not copy the user's wording back to yourself and treat that as understanding.
- Cross-check the restatement against available context. Look for contradictions, missing antecedents, or two plausible readings that context cannot choose between.
- If context resolves the read, proceed silently. Do not ask the requester to confirm what the available context already answered.
- If a real fork survives, surface one specific clarifying question anchored to the restated understanding. Name the choice; do not ask a vague "does this look right?"
- For substantial work, log one durable "understood as: ..." line before beginning so a later reader can audit whether the work matched the confirmed read.
Rules
- Restate, don't echo. A paraphrase proves you built a model of the request; a verbatim repeat proves little.
- Silent when context resolves it. The default good outcome is invisible. Surfacing a question for a resolved or unambiguous request is a defect.
- One fork at a time. If several ambiguities exist, surface the highest-stakes one first instead of dumping a checklist.
- Never silently resolve a fork that changes the shape of the work.
- Log large commitments, not every turn. Durable read logs are for plans, multi-file changes, irreversible actions, or work a fresh reviewer may need to audit.
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 · 34 lines · 88 tokens per session scan A ad031663c912
readchk is a skill published in the GitHub repository LilMGenius/paperthin (1,054 stars, last pushed 16d ago), licensed MIT. It adds 88 tokens to every session and 557 once invoked, about $0.0004 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
mm-init-project
Инициализирует или обновляет проект для mm-системы — создаёт passport.md в корне, копию в Obsidian, dashboard.md, handoff.md (скелет), project-instructions.md для claude.ai. Use when user says "оформи проект", "сделай паспорт", "init project", "/mm-init", "/mm-init-project", "обнови паспорт", "регистрирую проект".…
mm-setup
Онбординг/персонализация mm-системы под конкретного пользователя — спрашивает имя, чем занимается, стек, язык, путь к Obsidian vault, и записывает это в личный gitignored-оверлей config/mm-config.local.json + генерирует персональную копию claude.ai-скилла mm-web-bridge. Use when user says "/mm setup", "/mm onboard"…
mm-update
Самообновление mm-системы из удалённого репозитория. mm раздаётся через git clone + register-skills (не npm), поэтому update = git pull свежего mm из origin/main + повторный register-skills + notice о перезапуске Claude Code. Use when user says "обнови mm", "обнови систему", "/mm update", "update mm", "подтяни свежий…
mm
Диспетчер mm-системы — короткая команда вместо длинных. /mm без аргументов = список всех команд. /mm new = init project, /mm save = save session, /mm next = handoff, /mm prompt = bridge, /mm rules = instructions, /mm check = doctor. Use when user types "/mm" anything OR says "что есть в mm", "какие mm команды"…
content-editor
Writes and edits the portfolio's pages. Reads a brief, follows the style guide, and emits the HTML into public/.
notion-publish
Mirrors the portfolio's pages into Notion after publishing, creating one Notion page per site page via the Notion MCP. Use it from /publish, or when the user asks to sync the site to Notion.