Paperthin is a collection of low-level design patterns that coding agents can apply as repeatable checks and actions during software work. It is for people using agents such as Claude Code, Codex, Cursor, or other supported tools, and its catalogue entries package the patterns as skills, an instruction, and a plugin.
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 LilMGenius/paperthin --skill re0-plangit 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/re0-plan)<a href="https://agentmods.dev/skills/lilmgenius/paperthin/re0-plan"><img src="https://agentmods.dev/badge/skills/lilmgenius/paperthin/re0-plan.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00062 | $0.01266 |
| Opus 5 | $0.00031 | $0.00633 |
| Sonnet 5 | $0.00012 | $0.00253 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
re0-plan 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 today.
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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open .re0/iteration/<version>-<workname>/ and write into it in the same motion, before a single line of re0-loop's cycle runs.
Goal
A cycle without a written thesis, gate list, and step plan drifts to whatever framing comes first — and a folder opened with nothing in it tells a resumed session nothing at all. re0-plan closes both gaps at once: the folder is never empty from the moment it's created, regardless of which weight the cycle turns out to be. It assumes the full paperthin package installed and names its sibling skills directly. It pairs with re0-release, which retires the folder, and re0-memo, which extends whatever this skill seeded instead of restarting fresh. It is not a portable planning method — the shape it writes is this repo's own convention.
Workflow
- Classify the cycle's weight: a fix or hardening pass with no real design surface is lightweight; a cycle with a direction genuinely worth arguing through is full.
- Create
.re0/iteration/<version>-<workname>/and, in the same step, write its first file — the weight decides which:- lightweight →
RETRO.local.md: one paragraph naming the task and why it's lightweight.re0-memoextends this same file at the end; it never starts a fresh one. Stop here. - full →
DESIGN.local.md: thesis, scope, and quality gates — the same contentre0-loop's FRAME turn expects, and enough on its own to survive a session break. When the change touches shippable surface, those gates always include an AGENTS.md/README reflection gate (see Rules). Confirm the read withreadchk, size the tier withmodelchk; reach formacrothinkor another judgment skill only when the direction is genuinely contestable.
- lightweight →
- (full only) Write
WORKFLOW.local.md: the numbered steps this specific cycle runs throughre0-loop's turn order — specific to this build, not a restatement ofre0-loop's generic stages. - (full only) Write
EVIDENCE.local.md: the gates fromDESIGN.local.md, listed as proof surface still to fill — the bar, not results. - Keep reference material flat as
REF-<topic>.local.md; promote to arefs/subfolder only once it multiplies past a couple of files. - Hand off to
re0-loop. Do not invokere0-workhere — a from-scratch restart isre0-loop's own mid-cycle call, surfaced bynbawhen warranted, never a setup step.
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.
- today Changed 6df41243c031
- 8d ago First seen · 43 lines · 62 tokens per session scan A e4282013b6e6
re0-plan is a skill published in the GitHub repository LilMGenius/paperthin (1,077 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,266 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-30.
Other skills, from other repositories
mm-init-project
A project setup workflow that creates a shared project record in Markdown files, including a passport, dashboard, handoff notes, and instructions for Claude.ai. Obsidian is a note-taking app that can store these files as a connected project vault.
mm-instructions
A generator for ready-to-paste instructions for a Claude.ai project. It reads project details and fills a template with the project's name, technology, planning information, and current work context.
mm-projects
A read-only overview of all registered projects stored in Obsidian notes. It shows each project's status, type, current GSD phase, recent activity, and number of open questions.
mm-setup
A setup guide that personalizes a shared mm system for one user. It asks for details such as your name, work area, tools, language, and Obsidian vault location, then saves them in private configuration files.
mm-update
A guided updater for the mm system, which is installed by copying a Git repository rather than through a package manager. It downloads the latest version, registers its skills again, and tells you to restart Claude Code.
mm
A dispatcher that provides short /mm commands for project setup, session recovery, project overviews, and workflow checks. It maps these aliases to longer system commands.