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 wenlan-app/wenlan --skill curategit clone --depth 1 https://github.com/wenlan-app/wenlanWrote 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/wenlan-app/wenlan/curate)<a href="https://agentmods.dev/skills/wenlan-app/wenlan/curate"><img src="https://agentmods.dev/badge/skills/wenlan-app/wenlan/curate/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/wenlan-app/wenlan/curate"><img src="https://agentmods.dev/badge/skills/wenlan-app/wenlan/curate.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.00102 | $0.01852 |
| Opus 5.5 | $0.00041 | $0.00741 |
| Sonnet 5.5 | $0.00020 | $0.00370 |
| Haiku 4.5 | $0.00010 | $0.00185 |
Grade A, and why
curate 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- curate — 97% identical, 180 lines differ
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/curate
Power-user audit lever. Most users do not need /curate in daily flow:
- Pending revisions surface in
/briefautomatically (top 3 with inline accept/dismiss). - Pending captures from this session surface in
/handoff's preview block (top 3). - Orphan wikilinks surface in
/distill's topic-suggestion block.
Use /curate only when you want the deep walk those skills intentionally do not force.
Captures are meant to decay. A capture lands pending (not yet confirmed) and, if nothing
ever conflicts with it, it quietly fades — that is by design, not a backlog you owe the
system. The only items that need a human are genuine conflicts (a contradiction,
or a richer re-capture worth merging); those surface as pending revisions. /curate captures is an opt-in audit for when you want to seal a batch (e.g. after a
bulk import), not a daily chore to zero out.
Safety protocol
Perform no mutation until the user replies. Ambiguous replies do not mutate. Cancellation, no reply, or unclear syntax is a no-op.
Render at most four items at a time. Number every item. Ask for explicit action syntax:
1 accept
2 dismiss
3 skip
4 edit: <replacement text>
Do not rely on hidden pagination state across turns. After applying a batch, re-list before showing another batch.
/curate revisions (and bare /curate) → via the wenlan CLI
Revisions go through the CLI, not MCP, because revision actions must key on
the exact revision_source_id. Resolve the binary once, then list:
W="$(command -v wenlan || echo "$HOME/.wenlan/bin/wenlan")"
"$W" --format json curate
That prints a JSON array; each element is ONE logical revision (the CLI already groups the per-chunk rows and joins their text, so you never see a mid-sentence fragment):
revision_source_id— the staged revision; the action key for accept/dismiss. Keying on this (not the target) means the named revision is acted on even when several compete for one memory.target_source_id— the memory this revision would replace (context only).content— the full revised text.source_agent— who proposed it (ornull= daemon).original— the current text the revision would replace (nullif unavailable).diff— a card-ready, length-boundedOLD:/NEW:preview of what the revision would replace (two labeled lines, original then revision, each clipped).nullwhenoriginalis unavailable.
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.
- 3d ago Changed · +15 lines · +47 tokens per session ffd9de24310e
- 4d ago First seen · 160 lines · 55 tokens per session scan A 3be715e5213c
curate is a skill published in the GitHub repository wenlan-app/wenlan (82 stars, last pushed yesterday), licensed Apache-2.0. It adds 102 tokens to every session and 1,852 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-10-11.
Other skills, from other repositories
forget
Delete a Wenlan memory by exact id from Codex. Destructive and confirmation gated. Invoked as /forget .
recall
Search Wenlan's local memory from Codex by query. Targeted lookup, not session orientation. Invoked as /recall .
capture
Save a durable memory to Wenlan from Codex. Use proactively when the user states a preference, makes a decision, corrects you, or shares a durable fact. Invoked as /capture .
handoff
End a Codex work session. Stores durable captures, writes a narrative session log, and automatically applies typed item-level deltas to the current Space Brief. Invoked as /handoff.
lint
Lint Wenlan memory quality and hygiene, check vocabulary, or resolve every finding into a ready repair, review item, system action, or blocker.
run-wenlan-app
Build, launch, screenshot, and drive the wenlan-app Tauri desktop app in dev mode on macOS (WKWebView) or Windows (WebView2). Use when asked to run or start the app, verify a UI change in the real running app (not just tests), or take a screenshot of it.