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 byenzyme/enzyme --skill enzyme-workspace-setupgit clone --depth 1 https://github.com/byenzyme/enzymeWrote 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/byenzyme/enzyme/enzyme-workspace-setup)<a href="https://agentmods.dev/skills/byenzyme/enzyme/enzyme-workspace-setup"><img src="https://agentmods.dev/badge/skills/byenzyme/enzyme/enzyme-workspace-setup/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/byenzyme/enzyme/enzyme-workspace-setup"><img src="https://agentmods.dev/badge/skills/byenzyme/enzyme/enzyme-workspace-setup.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.00091 | $0.04412 |
| Opus 5.5 | $0.00036 | $0.01765 |
| Sonnet 5.5 | $0.00018 | $0.00882 |
| Haiku 4.5 | $0.00009 | $0.00441 |
Grade A, and why
enzyme-workspace-setup 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 yesterday.
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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enzyme Workspace Setup
Read references/knowledge-practice-review.md completely before interpreting the
notes or composing the handoff. It owns the shared judgment about the user's
practice; this skill owns Enzyme commands, permissions, changes, and recovery.
When delivered through MCP, that reference is appended inline.
The job
Help the user answer something they care about using the notes they already have.
You write the settings: compile --packet gives you the evidence Enzyme's
selection would use, and the user's AGENTS.md, CLAUDE.md, or router notes say
what matters and where it lives. Review the draft with the user, prepare search,
demonstrate one answer, and fix a problem only if the evidence warrants it. A working setup
with no note changes is a complete success. Tidiness is not a retrieval goal.
Keep the sequence explicit:
- Check the workspace and provider.
- Run
compile --packet, read the user's own map, write the settings, and review them with the user. - With setup and generation authorized, run
init, checkdoctor, and prove an answer. - Offer an optional repair only for a demonstrated problem; finish with what the user can do next.
These permissions cover different effects. Reuse explicit authorization already in the conversation; ask only for an effect or choice it has not covered. A plain request to set up Enzyme does not authorize sending excerpts, downloading a model, or editing notes. Never let an approval reviewer choose a provider for the user.
Talk about the user's work
Use actual note names, subjects, and questions. Until retrieval proves an answer,
say “we can try asking,” not “this now answers.” Call the program settings.
Explain the mechanism once: Enzyme prepares questions from the notes to help find
related passages. Describe selected folders/tags by the questions they may help
answer, not as “anchors,” “surfaces,” “tiers,” “profiles,” or “dedicated questions.”
Do not make the user learn a glossary or another unexplained metaphor. For a date
repair, say “I'll add date: 2026-08-26 above your writing. This edits the file's
date information; your writing stays unchanged.” Explain the backup as restoring
the file and its original date, not as frontmatter, byte identity, or checksums.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +6 lines ae0317e12372
- 8d ago Changed · +17 lines · +12 tokens per session d8f0de3a7e21
- 24d ago Changed · +2 lines 9444b40edc23
- 1mo ago Changed · +28 lines · -40 tokens per session 7bcb41790243
- 1mo ago Changed · +114 lines aff8ad61c0ba
- 1mo ago First seen · 177 lines · 119 tokens per session scan A 1fe2d35b4a95
enzyme-workspace-setup is a skill published in the GitHub repository byenzyme/enzyme (98 stars, last pushed yesterday), licensed Apache-2.0. It adds 91 tokens to every session and 4,412 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
ai-second-brain
Walks the user through Charlie Hills's AI Second Brain + Karpathy Wiki setup from the MarTech AI newsletter. Use whenever the user mentions building an AI second brain, the Karpathy wiki, organising their ChatGPT/Claude exports in Obsidian, setting up a living wiki with Claude Code, connecting iMessage Channels, or…
wiki-build
A tool for building or rebuilding a local wiki from all source files in a vault, which is a folder used to store source material. It creates structured pages, layered indexes, logs, and cross-links.
remotion
Molio's builtin skill for MAKING a video from any source — wiki notes, articles, scripts, product info, or a brief — and rendering it to MP4. Use whenever the user wants to create/produce a video: a product demo, promo, trailer, intro, explainer, motion graphic, kinetic typography, social clip, or animated logo — even…
wiki-ingest
A tool for adding source files or URLs to an existing local wiki. It creates or updates summary, topic, comparison, and index pages, with links between related pages.
docling
PRIMARY skill for converting .pdf, .docx, .pptx, .xlsx, .doc, .ppt, .xls, images, and audio/video files (.mp3, .wav, .m4a, .mp4, .mov, etc.) to Markdown. Always prefer this over the docx/pdf/pptx/xlsx/paddleocr skills — docling uses GPU-accelerated OCR + layout detection + table structure extraction for documents, and…
wiki-lint
A health checker for a local wiki, which is a collection of linked knowledge pages. It reviews the pages and produces a report about structural and content problems.