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/prismnpx skills add LilMGenius/paperthin --skill prismgit 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/prism)<a href="https://agentmods.dev/skills/lilmgenius/paperthin/prism"><img src="https://agentmods.dev/badge/skills/lilmgenius/paperthin/prism.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.00098 | $0.00653 |
| Opus 5 | $0.00049 | $0.00327 |
| Sonnet 5 | $0.00020 | $0.00131 |
| Haiku 4.5 | $0.00010 | $0.00065 |
Grade A, and why
prism 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Split one artifact across independent lenses and return where they converge and where they don't.
Goal
The result is a picture of where the lenses agree, where they disagree, and the smallest question that would resolve the disagreement. Not a checklist, and never an average — averaging the lenses is the failure this skill exists to prevent.
Workflow
- Read the artifact end to end before choosing the lenses.
- Choose one lens per genuinely distinct failure mode — correctness, security, readability, cost, adversarial-user, and the like. Two candidate lenses that share a failure mode are one lens, not two. In practice this lands between 2 and 5: below 2 there is nothing to converge, and past 5 you are almost always padding with lenses that overlap. There is no default count — the artifact's distinct failure modes set it.
- Through each lens, produce a one-line verdict — pass, fail, or unclear — with its single most load-bearing reason. No hedging list; if a reason isn't load-bearing, drop it.
- Compare the verdicts and group them: full agreement, agreement for different reasons, disagreement.
- Where there is disagreement, name the single next question whose answer would move it into agreement or a clean split with owners. That question is the output, not the individual verdicts.
- Where every lens agrees, return the shared verdict with the reasons that were load-bearing for at least two lenses.
Rules
- Independent lenses, not roles. A "security reviewer" and a "senior security reviewer" are one lens, not two.
- One reason per lens — the load-bearing one. A lens that returns a list is hedging.
- Disagreement is the product. A prism that agrees on everything did not need to be run.
- Never average. If two lenses split, the answer is the question that resolves the split, not the midpoint of their verdicts.
- Draw the lenses fresh for the artifact in hand. A lens useful for a spec may be useless for a migration; don't carry lenses across artifacts.
- Don't manufacture disagreement. A run that finds none returns the shared verdict and stops.
- User-invoked on purpose: plural lenses are an opt-in spend, and their convergence must never masquerade as automatic proof, so this fires only when deliberately reached for.
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 · 35 lines · 98 tokens per session scan A c7ed6a24e508
prism is a skill published in the GitHub repository LilMGenius/paperthin (1,054 stars, last pushed 16d ago), licensed MIT. It adds 98 tokens to every session and 653 once invoked, about $0.0005 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.